Approvals Inbox

One place to decide

When the Action Bus routes something to a human, it lands here. That includes agent R3 Actions, discounts and refunds above DoA limits, policy changes, legal holds, data requests and incident notifications, and later leave, expenses and pay runs from People and Finance. A first version runs inside automations from Wave 0, with the full inbox in Wave 1.

A clear preview

Each request shows what will happen: a diff, the rendered message or the amount, the risk tier, a reversibility warning, the AI rationale and an expiry. Approvers can approve, reject with a required reason, edit and approve (which re-validates), or ask for more information. The underlying workflow resumes or cancels durably on decision or expiry.

The right approver

Assignees are resolved through the DoA matrix by membership, group or role, with sequential, parallel or N-of-M multi-approver routes. R4 and legally irreversible decisions need step-up authentication. Segregation of duties is enforced: the requester cannot approve, an agent never approves, and the preparer cannot approve where declared.

Decide from anywhere

Planned for Wave 2: approvals in WhatsApp with identity verification and audit, and approvals in the PWA with web push. Delegation covers out-of-office with a date range and scope, recording both identities. Escalation sends reminders, escalates on SLA breach and auto-expires with a configured outcome. It never auto-approves R3 or above.

Better decisions over time

An AI approval summary explains what changes, who is affected, risk factors and similar past decisions with citations. Bulk approve works only for homogeneous R2 or R3 requests within policy, never R4 and never mixed risk. A decision journal links decisions to later outcomes. Approval analytics show cycle time, rejection reasons and rubber-stamp detection. Client approvals inside the agency portal let client users approve creative and campaigns.