> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Approvals in workflows

> Gate Ravenna workflows on approval: add approvers with Add Approval Round or Apply Approval Template, pause with Wait for Approval, and handle approved, declined, and timed-out requests.

Use approval steps to stop a workflow until the right people approve a request, then continue down a different path for approved, declined, and timed-out requests.

## Approval steps

| Step | Role | Notes |
| - | - | - |
| Add Approval Round | Adds one round with approvers, policy, and assignment strategy | Resets the ticket's approval to in progress |
| Apply Approval Template | Replaces all existing rounds with a template's rounds and starts the first | Template skip conditions and dynamic approvers apply |
| Add Approvers | Older action superseded by Add Approval Round | Prefer Add Approval Round in new workflows |
| Wait for Approval | Waits for the ticket's overall approval, with a timeout (default 3 days) | Branches On Approved, On Declined, On Timeout |
| Ticket Approval trigger | Starts a workflow when a ticket's approval is approved or declined | Branches Approved, Declined |

## Behavior

* Approval Policy options: Any can approve (default), All must approve, Majority must approve.
* Assignment Strategy options: All (default; every listed user is an approver), Round Robin (one user, rotated), Auto Approve (the workspace bot approves immediately).
* Auto Approve only applies when the ticket has no active round. Otherwise the step adds every listed user, as with All.
* Ineligible approvers (deactivated, bots, not in the organization) are dropped before the strategy runs. If none remain, the step is skipped, a private note is posted on the ticket, and the path stops.
* Wait for Approval returns immediately when the ticket's approval has already completed or been declined.
* On Approved runs when Is Approved is true, including force approval. On Declined runs only when Is Approved is false and the wait did not time out. On Timeout runs when the duration elapsed with no decision.
* Outputs on Wait for Approval: Is Approved, Approved By, Declined By, Force Approved By. The Ticket Approval trigger outputs Is Approved, Approved By, and Declined By.
* Workflow outputs carry the deciders' user IDs, not the decline reason. Ravenna posts the reason on the ticket itself.
* All three branches of Wait for Approval carry conditions, so connecting two of them into one step means that step never runs. Rejoin from the last step on each path instead.

## Recipes

**Single approver with escalation:** Add Approval Round (manager, Any can approve), then Wait for Approval (2 days). On Approved: fulfill the request. On Declined: notify the requester. On Timeout: Add Approval Round (backup approver), then a second Wait for Approval.

**Conditional approval:** If / Else on a form field (for example, cost over a threshold). True: Add Approval Round with the finance group. False: Add Approval Round with Auto Approve. Then one Wait for Approval reached from the last step on each path.

**Multi-round chain:** Apply Approval Template (manager, then security), then Wait for Approval. The wait finishes when the final round completes.

**Decoupled follow-up:** keep the request workflow short, and build a second workflow on the Ticket Approval trigger, filtered to the channel, that provisions on Approved and notifies on Declined.

## Anti-patterns

* Putting stalled-request handling on On Declined. A timeout goes down On Timeout.
* Relying on Auto Approve to clear an approval that's already in progress. It falls back to adding everyone.
* Naming individual approvers who may leave. Use user groups so the round always has eligible approvers.


## Related topics

- [Approvals](https://docs.ravenna.ai/documentation/tickets/approvals/overview.md)
- [Workflows](https://docs.ravenna.ai/documentation/automate/workflows/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.