SupportDesk Starter Community

The full blueprint

Every agent's tasks, every table's schema, every trigger. Read it all before you sign in.

How the install works

1. Overview. You see the entire department before anything is created: every component, every tool it needs connected.
2. Setup questions. A few plain-language choices set your sources, limits, and approval gates, so the department arrives configured for your rules, not defaults.
3. Conflicts. Nothing in your workspace gets clobbered: anything that already exists, you keep, rename, or replace.
4. Install. Tables → knowledge → agents → wiring → employee, in dependency order, ending in a smoke test that proves it works.
5. Done. A working department, not a project plan. Open your new coworker and assign the first task.

Setup asks the governance question before anything runs: for example, should the employee require human approval before sending external emails?

Built on

Connects to

Governance defaults

• Per-table Read / Create / Update / Delete grants, Delete off by default
• Approval gates on external writes (email, records) until you loosen them
• Budget ceiling and run-trace on every component