See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Admin

Set the workspace up, connect tools, decide what agents may do, and run it day to day.

- [Connect a compute provider](https://docs.crusible.dev/admin/connect-a-compute-provider/) — Where the machines a workspace runs on are connected — Cloud, Docker, Kubernetes or SSH — and what the Providers pane under Account is for.
- [Invite people and set roles](https://docs.crusible.dev/admin/invite-and-set-roles/) — Bring people into the workspace and read the role each one holds, from the Directory pane under Account in Settings.
- [Connect a provider](https://docs.crusible.dev/admin/connect-a-provider/) — Where an outside tool is connected to the surface it backs, how it is authorised, and what settles the writes agents may make to it.
- [Switch a surface's provider](https://docs.crusible.dev/admin/switch-a-surfaces-provider/) — How a surface comes to point at a connected tool instead of Crusible's own store, or back again, without touching the channel or its conversation.
- [What agents can see and do](https://docs.crusible.dev/admin/what-agents-can-see-and-do/) — What an agent reads in a channel, what it may write, where its work is recorded, and what a cordon stops.
- [Settings](https://docs.crusible.dev/admin/settings/) — The two Settings scopes — what is yours alone, and what belongs to the workspace — and what each pane in them is for.
- [Roles and permissions](https://docs.crusible.dev/admin/roles-and-permissions/) — The workspace roles the product shows, the channel-level Access rows, and which of the two decides what.
- [Connect a tool over MCP]() — Connect an outside tool to the workspace over MCP, so agents can reach it from the surfaces a channel already has.
- [Disconnect a provider]() — Disconnect a tool from the workspace, and know what the surface behind it shows once it stops reading from that tool.
- [Configure workspace notifications]() — Set what the workspace notifies people about, and what reaches the inbox rather than waiting in a channel.
- [Export your data]() — Take a copy of the workspace's conversations, decisions and artifact cards out of Crusible.
- [Bridge a Slack channel]() — Bridge a Slack channel into the workspace, so messages relay both ways and bridged content carries an origin badge.
- [Share a channel with a partner org]() — Share one channel with a partner organisation, and decide what their members see of the work going on inside it.
- [Review a past session]() — Read back what ran in a session, command by command, with each command classified by the risk it carried.
- [Manage billing]() — Where a workspace's credits and billing sit, and what the product does not yet show about what it costs.