Approvals

Approvals is the queue where unattended work stops and asks. When Jarvis runs while you are not watching and reaches an action that would leave your company, it does not take it. It writes down exactly what it wanted to do and waits here.

This only applies to autonomous runs. In a normal conversation you are the approval loop: you see every step as it happens and can stop it, so nothing is queued.

What a proposal looks like

Each item in the queue shows the action it wants to take, named by the tool and the operation, a plain description of what it would do, and when it was proposed. You can expand it to see the exact payload the agent assembled. Not a summary of the email, the email.

Two buttons:

• Approve. Agently replays the action exactly as proposed. Nothing is re-generated between your approval and the send, so what you read is what goes out.
• Reject. The action never happens and the run moves on without it.

If an approved action fails on the way out, say because the connected account needs re-authorising, the proposal stays pending with the error attached so you can fix the connection and approve again.

What gets proposed, and what does not

Every action Jarvis can take in a connected tool carries a risk class, and each class has a default:

So an unattended run can read your CRM, update a record, and draft a reply on its own. Sending that reply to a customer stops here. Deleting the record does not happen at all.

You can override any of it per workspace, per tool, or per individual action. You can also raise the default for everything, or pull the single global switch that forbids all actions, which beats every other setting.

Where notifications live

Approvals is not your notification centre. Task updates, run completions, and workspace events arrive in real time in the notification drawer, reachable from anywhere in the app. Approvals holds only the things waiting on a decision from you.

A task that is stuck for a different reason, because Jarvis needs an answer from you rather than permission, waits under Needs you in Work instead.

Using it well

1. Check it before the routines fire. A pending approval holds up whatever run is behind it.
2. Set the policy once, per tool. If you never want Jarvis emailing customers directly, block that action rather than rejecting it every morning.
3. Read the payload, not the description. The expandable view is the point of the screen.

Related pages

• Work, the queue, including tasks blocked on you
• Routines, the standing instructions that generate unattended runs
• Security & Privacy, how connected accounts and audit trails work
• Meet Jarvis, how the agent decides to act