Approvals
Human-in-the-loop approval workflows for AI agent actions and sensitive operations
Approvals: 1 pages
The Approval system gives you control over what AI agents can do autonomously. Set up rules that require human review before sensitive actions are executed — like posting to social media, publishing landing pages, or creating records in specific modules.
How It Works
- Define rules — Admins create approval rules that match specific actions (e.g., "all social posts require approval")
- Agent triggers action — When an agent attempts a gated action, the system checks for matching rules
- Approval requested — If a rule matches, the action is paused and an approval request is created
- Reviewer decides — The assigned reviewer (manager, role, specific user, or record owner) approves or rejects
- Action resumes — Approved actions are automatically executed; rejected actions are cancelled
Creating Approval Rules
- Navigate to Admin > Approvals
- Click Create Rule
- Configure:
- Resource type — What kind of action triggers this rule (agent action, record mutation)
- Action type — The specific action (post to social, create landing page, create record, etc.)
- Conditions — Optional filters to narrow when the rule applies
- Primary resolver — Who should approve (named user, manager, role, record owner, or auto-approve)
- Fallback resolver — Backup reviewer if the primary is unavailable
Resolver Types
| Resolver | Description |
|---|---|
| Named user | A specific person always reviews these requests |
| Manager | The requesting user's manager (set via User Settings) |
| Role | Anyone with a specific role (e.g., all admins) |
| Record owner | The owner of the affected record |
| Agent | Another AI agent can auto-review (for lower-risk actions) |
| Auto-approve | Automatically approved after a delay (useful for logging without blocking) |
Gated Agent Tools
By default, approval rules can gate these agent actions:
- Post to social — Social media posts
- Create landing page — Public landing pages
- Create record — New records in specified modules
- Update record — Modifications to existing records
- Browse website — Computer use / browser automation sessions
Agent Email
Sending email works differently from the rules above. When a workspace Owner or Admin has turned on Agent email (it's off by default), an agent you're chatting with can ask to send a message from your connected mailbox. Every one of those requests needs your own approval of the exact email:
- The approval card shows the sender, recipients, subject, and body exactly as they will be sent, with an Approve & send button
- Only the person who asked can approve it — approval rules, resolvers, auto-approve, and other agents never apply
- Approve it on the card in the Coherence app; replying "yes" in chat or by email does not approve it
See Agent Email for the full rules and limits.
Reviewing Pending Approvals
Reviewers can see pending approvals in their Approval Inbox:
- Navigate to Approvals in the sidebar
- Review the pending request details (who triggered it, what action, context)
- Click Approve or Reject
Approved actions resume automatically. The agent task is re-queued and executed with the original parameters.
Expiration
Approval requests have an optional expiration time. If a request isn't reviewed before it expires, it's automatically marked as expired and the action is cancelled. Configure expiration per rule.
Permissions
| Permission | Roles |
|---|---|
approval:manage | Admin, Owner — create and manage rules |
approval:resolve | All users — review and resolve pending approvals |
approval:view | Manager+ — view approval history |