The controls

Autonomy without controls is not a feature, it is a liability. These are the four things that make it reasonable to let software work on your company overnight.

The approval queue

Every recommendation, escalation and sensitive action lands in one queue. Each item carries three things:

• The full content — the actual post, the actual email, the actual page change. Not a summary of it.
• The policy that made it need a decision.
• The audit trail behind it: what was done, by which agent, with which tool.

Approving releases it. Rejecting blocks it. There is no third state where something goes out because nobody looked — and if the queue is growing, that is itself the signal that the machine is stalled, not that it is being careful.

The spending cap

An agent may only spend up to a set amount without asking. Above it, the work stops and becomes an approval.

Two separate limits are worth keeping apart:

• Platform credits — what autonomous work draws down. A single task is capped, so no one night can drain a balance.
• Ad budget — paid on your own ad account. Every change to it is its own approval, never a footnote inside another one.

The vault

Credentials for connected systems are stored encrypted and are never handed to an agent as text. An agent asks the platform to use a connection; it does not get to see the key.

The connected app hub is the front of this: log in once to mail, calendar or storage, and every later use runs through that grant — scope-checked, rate-limited, logged.

The record

Every tool call is recorded: which agent, which tool, which model saw the data, what came back. That log is what turns “the AI did something” into something you can inspect afterwards — and what an EU AI Act file expects to find.

Alongside it, the file library keeps every document, image and file an agent produced or received, attached to the task that created it. Nothing an agent made is orphaned from why it made it.

More than one person

Data and permissions can be separated between teams or clients inside one account, with roles deciding who may approve what. An agency running five clients does not need five accounts, and the person who may approve a post is not automatically the person who may change a budget.

Where this lives

• Company → Approvals — the queue
• Company → Connections — grants and connected accounts
• Company → Files — the library
• Settings → Billing — caps and wallets

Where to read next

• How Autopilot works — what happens between two approvals
• What Autopilot costs — how the caps relate to your plan