Chief control centre

The Chief control centre, in the Agents menu, is where owners and admins decide what Chief may do in the workspace, and where everyone who uses Chief can see what it did. Owners and admins see every tab; anyone else who can use Chief sees the switches and their own activity. The Chief control centre is being switched on workspace by workspace; until it reaches yours, the page says so.

• The switchesChange records: Chief can create and update records, set reminders and file tasks when you ask. When off, Chief does not create or change records, set reminders, file plans or approvals, or send messages. It can still look things up, remember what you tell it, and run your background tasks and routines, which then only read.Drive the screen: Chief can open pages and fill in forms for you; you still press Save. When off, it tells you where to go instead.Talk to Chief: people can talk to Chief out loud. When off, Chief is typing only.Live voice: the natural voice you can talk over. It needs Talk to Chief, so it is off whenever Talk to Chief is off.Background tasks and routines: Chief can work on tasks while people get on with their day, and run routines on a schedule.Outside apps: Chief can use the apps connected on the Connect an app page.
• Assistants connected through MCPAn outside assistant working in your workspace through an MCP key (Administration ▸ API keys ▸ Assistant access) is governed by that key’s own scope, read-only or read and write, not by these switches. That page has its own two switches for outside assistants: one turns all assistant access off, reading included; the other stops their changes.
• Who can change themOnly workspace owners and admins, and only while the Edit permission for the Chief control page is ticked for their role in Roles & permissions. Everyone else who can use Chief sees the switches but cannot change them. A switch applies to everyone in the workspace, on every device, and it is enforced on our servers, not just hidden on the screen. Every change to a switch is recorded in the Activity log, with who made it.
• ActivityEvery step Chief took, newest first: when, what it did and on what kind of record, whether it worked or is waiting for a yes, and how long it took. Choose a period (today, 7, 30 or 90 days) and a result, and download what you see as a CSV. Owners and admins see everyone’s steps and can pick one person; everyone else sees their own. Why a step did not work, and Open in Chief to carry on that conversation, appear only for the person whose step it was.
• UsageOwners and admins only. Chief use by person counts each person’s questions, the steps Chief took for them and the changes it made, never what they asked. AI cost by model shows the calls, tokens and cost of the whole workspace’s AI use (Chief and the other AI features) over 7, 30 or 90 days, with the total. Cost by person is not measured yet.
• “via Chief” in the audit logChanges Chief makes on our servers are recorded as the person’s own, with “via Chief” beside their name in the Activity log (the audit log), or “via a Chief task” when one of Chief’s background tasks made them. That is what Chief does with its own tools while it works out an answer, and everything a background task does. Both mean our servers made the change through Chief.Changes made in your own browser are recorded as yours, with no label, including ones Chief prepared or made for you there: a quick create from a short command in the Chief panel (such as “create a task called Follow up”), a record it proposed that you confirmed, a form it filled that you saved, a workflow or invite you accepted.“via an MCP connection” means the change came through a connected assistant’s MCP key. Anyone holding the key can use it, so the label says how the change arrived, not that an AI made it.