Skip to main content
Governance is the reason Sidekick is safe to give real work. External and sensitive actions do not just happen. They pass through controls, and the thread records exactly what occurred. This is the differentiator. When a thread wants to run an external or sensitive tool call, it stops at a consent gate before the call runs. You decide how far your permission extends:

Once

Allow this single call. The next time the same tool is needed, you are asked again.

This thread

Allow the tool for the rest of this thread, without re-asking each time inside it.

Always

Allow the tool going forward, so future threads do not stop for it.
The gate is per tool, so allowing one capability does not grant others.

​
Some tools also require admin approval

A consent gate is your decision. Some tools additionally require workspace-admin approval before they can run at all. In that case the call waits until an admin signs off. Your own consent is not enough on its own; the admin approval is a separate, required step.

​
Resumption is always your explicit Continue

After an approval is granted, the work does not restart on its own. You resume it with an explicit Continue. Nothing runs the moment approval lands.
Sidekick never auto-resumes work after an approval. The person in the thread always presses Continue. This keeps a clear, deliberate boundary between “approved” and “running.”

​
The thread is a faithful ledger

Every part of this is recorded in the thread: what ran, what was asked for, who allowed it, and what it produced. Because the thread keeps that record, governance is not a promise made outside the work. It is visible in the work itself, and it stays replayable.

​
Where to go next

Approvals you'll see

What consent gates and approval prompts look like while you work.

Approvals and policy

How admins decide which tools require approval and who can grant it.