Skip to content

Approvals

An approval is a request from an employee to a human before it performs an action. The run pauses at a checkpoint until someone answers, then resumes from exactly where it stopped.

An employee asks for approval before an action when any of these is true:

Reason Example
Autonomy level At L1 Approve, every Write internal, Communicate and Spend action. See Autonomy levels.
Threshold At L2 Act within limits, a payment of 25 USDC when the limit per payment is 10 USDC.
Irreversible action Deleting records, signing, publishing publicly, unless a policy explicitly allows it.
Policy A policy requires approval, such as “Any email to a customer marked VIP”. This applies at every level, including L3 and L4.
Budget The action would exceed the employee’s budget or spend limit.
Employee’s own judgment The employee is unsure, for example when instructions conflict. It can always ask, even when it doesn’t have to.

Each approval contains:

  • the action the employee wants to take, with its exact content, such as the full email or the payment amount and recipient,
  • the reason it’s asking: the rule, threshold or policy that triggered it,
  • the context: the task, a summary of the run so far, and a link to the full run,
  • the impact class, cost and whether the action can be undone,
  • a Probation badge if the employee is still in probation.

Approvals go to the employee’s human manager by default. They appear in:

  • the Inbox in Orqane, with filters by employee, team, impact class and age,
  • Slack or Microsoft Teams, as a direct message with action buttons,
  • email, with a link to review and answer in one click,
  • the Orqane mobile app, with push notifications.

Choose your channels in Settings > Notifications. You can answer from any of them. The first answer wins, and the others update to show who answered.

Action What happens
Approve The employee performs the action exactly as shown and continues the run.
Request changes You say what to fix. The employee revises the action and asks again. Your feedback is saved to its memory.
Reject The action isn’t performed. The employee continues without it, finds another way, or stops and reports, depending on the task. Add a reason so it learns.
Take over You take control of the run. Edit the action, do it yourself, then Hand back or finish the task. See Take over a run.

You can edit the content before you click Approve, for example to fix a sentence in an email. The employee sends your edited version and records the difference.

An approval that nobody answers moves up an escalation chain:

Step Who receives it Default delay
1 The employee’s human manager Immediately
2 The team owner After 4 hours without an answer
3 Workspace Admins After 8 hours without an answer

Everyone earlier in the chain can still answer. After 24 hours without an answer, the approval expires and is treated as Reject. The task owner is notified.

Change the delays, the chain and the expiry on the employee’s Autonomy tab, or for every employee in a policy. Tasks with a deadline use a shorter expiry when needed, so an approval never expires after the deadline. When a human manager is out of office, set a Delegate in their profile to receive their approvals instead.

When an employee prepares many similar actions, such as 30 follow-up emails, it groups them into one batch approval. Open it to see each action in a list.

  • Click Approve all or Reject all.
  • Or select some items, then approve, reject or request changes on those only.
  • Open any item to edit it before you approve.

The employee performs approved items and skips the others. Batches contain up to 100 actions.

Approval rules let you change who approves, and when, without changing autonomy levels. You set them inside a policy.

Rule Example
Require approval Any payment to a new merchant needs approval, at every level.
Route to a specific approver Refunds above 200 EUR go to the finance team owner.
Require two approvers Contracts above 10000 EUR need the human manager and an Admin.
Auto-approve Internal Slack messages in #ops are approved automatically, even at L1.
Restrict hours Approvals created outside business hours wait for the next business day instead of escalating.

Every approval and answer is recorded in the audit log, with who answered, when, on which channel and what changed.