Approvals

When an agent task proposes a high-risk action, it pauses and waits. It will not proceed until a person with the right role reviews the request and makes a decision. That decision is yours.

Note

Approvals are the human checkpoint built into Zahen. Every high-risk action must pass through this flow before the platform will execute it. There is no way to bypass it.

Who this section is for

You need the approver, department admin, or platform admin role to act on approval requests. If you can see the Approvals queue in the sidebar, you have at least one of these roles. See What your role lets you do if you’re unsure.

How it works

1. An agent task reaches a step that proposes a high-risk action.
2. The task pauses — its status becomes awaiting approval.
3. An approval request appears in the Approvals queue.
4. You open the request, review the proposed action and the evidence the agent assembled, and make a decision.
5. If you approve, the task resumes automatically from where it paused. If you reject, the task stops without performing the action.

Nothing happens to the task while it is paused. It holds its state and waits as long as needed.

In this section

• Reviewing a paused task — what you see when you open a request: the proposed action, its risk level, and the supporting evidence.
• Making a decision — the five outcomes available to you and what each one does.
• The approvals queue — the centralised list of pending and historical requests.

To understand why certain actions trigger this flow, see Risk levels & approvals.