Skip to main content
Open Sidekick → Approvals to work the admin queue: every tool approval, admin approval, and budget request waiting on a decision.

What lands in the queue

Tool approvals

A connector call that hit a gate requiring admin sign-off, beyond whatever consent the person running the thread already gave.

Admin approvals

An action a member can’t clear on their own, regardless of which tool is involved.

Budget requests

A request to raise a spend cap that a person or agent has hit. See Budgets.

Approve or deny

1

Open an item

Each item in the queue shows what’s being asked for, who or what it’s for, and a risk recommendation describing why it needs a decision.
2

Read the risk recommendation

The risk recommendation is a summary of what makes this item worth a second look, not an automatic decision. It’s there to inform your call, not replace it.
3

Approve or deny

Approving clears the item and lets the underlying action proceed. Denying blocks it. Either way, the person or thread it came from is notified of the outcome.
Approving a tool or admin approval doesn’t resume the thread automatically. The person in the thread still presses Continue on their end.

Where to go next

The governance model

How consent gates and admin approval work together to keep sensitive actions in bounds.

Approvals

What an approval card looks like from the member’s side, and how they respond to it.