Skip to main content
Private Beta — Contact us to get set up.
Some operations shouldn’t execute immediately. Deleting a user account, exporting customer data, revoking access—these warrant a second pair of eyes. Approval workflows add human oversight where it matters.

​
Risk classification

Tools are classified by risk level:
ClassDescriptionExamples
L0Read-onlylist_users, get_document, search_tickets
L1Writecreate_ticket, update_record, send_email
L2Destructivedelete_user, revoke_access, close_account
L3Data exportexport_customers, download_report, bulk_extract
L0 operations auto-approve—they don’t change anything, so there’s no risk in executing immediately. L1 operations can be role-gated. A manager might self-approve writes in their domain; a junior employee might need their manager’s sign-off. L2 and L3 always require explicit approval. Someone with authority must review and approve before execution.

​
The approval flow

When a user calls a tool that requires approval: The user gets immediate feedback that their request is pending. They can continue other work while waiting. When the approver acts, the result flows back.

​
Who approves

Approvers are determined by configuration: Manager chain routes to the user’s manager (pulled from your IDP). Managers approve for their reports. Role-based routing sends to users with specific roles. An approver role, a security-reviewer role, whatever fits your org structure. Tool-specific approvers can be set per-tool. The database admin approves database operations; the security team approves access revocations. Escalation handles timeouts. If the primary approver doesn’t respond within a window, the request escalates to the next level.

​
Timeout behavior

Requests don’t wait forever. You configure what happens when approval times out:
  • Deny — Request expires, user notified, must resubmit
  • Escalate — Route to next approver in chain
  • Allow — Auto-approve after timeout (rarely appropriate for L2+)
Most organizations deny on timeout. If a request was important, the user will resubmit. Auto-approval defeats the purpose of the workflow.