Approvals
The queue of actions that need a human yes/no before they continue.
Admin → Approvals is where actions that Ian On won't take on its own wait for a person. It's the human checkpoint that keeps automation accountable. Requests waiting for you also show up under Home → Needs your attention → Pending approvals, and clicking one opens the screen where you decide it right away. Delivery requests don't show up on Home, so check them here.
Only the Owner and Admin roles can open Admin → Approvals. A request tied to a piece of work is decided in that work by its assigned reviewer, whatever their role.
There are three tabs: Delivery, Runtime, and All. All opens by default and shows both kinds of pending requests together.
- Delivery — something is about to be sent out (an email, a report to an external channel) and the policy gate wants a human to confirm the recipient and content first.
- Runtime — a database query caught by a rule set to Approval required in Data access policies under Database connections. Approval requests from work where you're the assigned reviewer show up here too. (Confirming a plan before a piece of work starts doesn't go through this queue. See Work.)
You Approve or Reject delivery requests and database query requests right on this screen. For a request tied to a piece of work, click Decide in Work to open that work's Execution details, and decide there. The Decision note is optional. Decided requests drop off this list. For requests tied to a piece of work, once the work is finished you can see who approved or rejected them in its record in History.
Work that's waiting for approval shows Awaiting approval. Blocked is a state separate from approval: check the cause in that work's Execution details, then retry.