Approvals
Actions your agents, chatbots and workflows held for a person, and how to decide them safely.
The model only proposes actions. ORYVOX's tool firewall decides whether each one runs, waits for a person, or is blocked. Everything that waits for your team lands in Approvals.
What waits for approval
- tools set to Team approves in a chatbot or agent;
- actions your security policy holds, such as refunds and payments above an amount;
- workflow steps marked Approval required;
- deleting data in a connected system.
Visitor confirmations (a booking the visitor must confirm in the chat) expire after 30 minutes; team approvals after 7 days.
Decide
- 01
Approvals → Pending → a request.
Open Approvals → Pending. Each request shows exactly what would be sent, who or what asked, the conversation or run it came from, the risk, and when it expires.
- 02
Safeguards
- Maker-checker: the person who requested an action can't approve it when its policy forbids self-approval. Owners get no bypass.
- Step-up: risky approvals ask for your password again.
- One decision: two people clicking at once can't approve twice.
- Audit: every decision is recorded, and for financial or delete actions nothing runs without the audit entry.
Approvals can also be answered in Slack. Tabs show Pending, Approved, Rejected and Expired. You need the tools.approve permission (or workflows.run for workflow steps).