Admin Guide

The Admin Guide covers the decisions that apply to everyone in a workspace: who is a member and what their role permits, which integrations exist and which of their tools are enabled, how much Quickly is allowed to do without asking a human first, and how programmatic access is granted through API keys and the MCP server.

The most consequential page here is Autonomy Controls. It determines whether a write action runs immediately or waits for approval, and it can be set for the whole workspace, per integration, per tool, and per role. Most teams start restrictive and loosen it once the action logs show them what Quickly actually does.

Action Logs is the other page worth reading closely. Every tool call is recorded with its outcome and the policy decision that permitted it, which makes it both the audit trail and the evidence you need when deciding what to automate next. Analytics is the aggregate view of the same work.

Two constraints shape everything in this section. Integrations are authorized per person, so an Admin decides which integrations and tools exist but cannot connect an account on someone else's behalf. And roles govern visibility as well as permission, so a Member simply does not see the doors they are not allowed to use.