Skip to main content
Approvals add a review step (“four eyes”) before actions that move money. When a policy applies, the action waits for an approver instead of running right away.

Which actions can require approval

Policies

Each action has a policy with three settings: Only workspace admins can change policies. Policies are read with GET /v1/approvals/policies, and updated with PUT /v1/approvals/policies/:action.

Example: approve any credit grant over $500

Request lifecycle

When an action that needs approval is requested, Orvlin creates an approval request instead of running it.

Working with requests

  • List requests: GET /v1/approvals.
  • Read one: GET /v1/approvals/:id.
  • Approve: POST /v1/approvals/:id/approve with an optional note.
  • Reject: POST /v1/approvals/:id/reject with an optional note.
Every decision is recorded in the audit log, with the approver and the note. Orvlin also sends webhooks for approval events, so your team can route requests to Slack or a ticketing system.
Start with thresholdAmount set to a value that catches only the risky cases. Review the queue for a week before you tighten it.