Help · Surface
Admin
The org account, for verified members. Open /admin on the web, or the Admin link in Settings.
Five pages
Settings is about you. Admin is about the org. Devices and Connected Claudes appear on both: Settings shows yours, Admin shows the org's.
| Address | Holds | Changes |
|---|---|---|
/admin | Operations: what is happening, the meetings hosted, the usage ledger and its thresholds, the failures the Worker counted about itself in the last seven days (refused signatures, Core's events gone quiet, a route answering 5xx, a deploy check that could not run), LiveKit participant-minutes, measured downstream RTP receive bytes with the latest client-report time, Connector calls: every MCP call, with client, tool, outcome and whether a retry replayed its first result, and, for org admins, model calls and tokens per day | read-only |
/admin/agents | Agents: each agent's identity avatar, plus the last 30 days of handoffs, runtime acceptance or refusal, finalized replies observed by Starlings, delivery issues, watchdog reset outcomes, each configured endpoint's origin, and whether it is frozen, when and by whom | freeze, unfreeze |
/admin/people | People: the human roster and Changes | visibility, role, access, devices; hide, restore, revoke; sign a device out |
/admin/connectors | Connectors: the environment rows from the deploy at the top, then Granola, GitHub, Slack and the Mac recorder; each card opens its page at /admin/connectors/<source> | mappings, Sync now, backfill |
/admin/jobs | Jobs: the one-off admin actions, each with what it touches and when it last ran | the jobs themselves |
Any verified member can read these pages. Only an org admin can make changes.
The monthly downstream figure is the sum of RTP media bytes received by browser, Mac and iOS clients. Clients report about once a minute, and Admin refreshes automatically. It shows observed bytes only: it has no plan cap or projection, omits data-channel and transport overhead, may miss clients that have not reported, and can differ from LiveKit's billed total.
Freezing an agent
Freeze on /admin/agents stops one agent from its next call, with no
deploy. A frozen agent gets no messages, cannot read Starlings and cannot post.
A person who writes to it sees a quiet line in the conversation saying it is
frozen. Unfreeze lets it back in. Admin's trail records who did each.
Leads to
A meeting's transcript; a person in team.
Verified · docs/help/surfaces/admin.md