> ## Documentation Index
> Fetch the complete documentation index at: https://forest-chore-open-api.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Approval workflows
> Review, approve, or reject actions that require team validation before execution.
The **Approval Workflow** feature lets your team ensure that sensitive or high-impact actions are reviewed before they execute. When an action requires approval, it is held in a queue until a qualified team member approves or rejects it.
This is especially valuable for large teams that need structured, controlled decision-making, ensuring every critical action is reviewed and audited.
## How it works
1. An operator triggers an action that requires approval.
2. Instead of executing immediately, an **approval request** is created.
3. Team members with approval permission are notified and can review the request.
4. Once approved (or rejected), the action either executes or is cancelled.
5. The request moves to **History** for audit purposes.
## The approval workflow screen
Navigate to the **Collaboration** tab → **Approval Workflow** to access the approval queue. Requests are divided into three lists:
| List | Description |
| ------------- | ----------------------------------------------------------- |
| **Created** | Approval requests you have submitted and are pending review |
| **To review** | Requests you have permission to approve or reject |
| **History** | All processed requests (approved or rejected) |
## Reviewing a request
Click on any approval request to open a modal showing:
* The **action** that was triggered and its name.
* The **target record** the action applies to.
* The **form values** entered by the requester (if the action has a form).
After reviewing, you can:
* **Approve**, the action will execute immediately.
* **Reject**, the action is cancelled; the requester is notified.
* **Comment**, leave a note explaining your decision.
Once processed, the request moves to **History**.
## Filtering approval requests
For large teams with high request volumes, use the **filter panel** to narrow the list:
| Filter | Description |
| ----------------- | --------------------------------------------------- |
| **Action** | Filter by the name of the action |
| **Requester** | Filter by the team member who submitted the request |
| **Team** | Filter by the team associated with the request |
| **Creation date** | Select a date interval |
Multiple filters can be combined for precise results.
## Exporting approval history
Click the **Export** button in the History section to download a CSV of your approval requests over a given time period. The file will be sent to your email.
## Configuring approval workflows
Approval workflows are configured in **Project Settings → Roles**. For each role, configure each action's approval behavior:
| Permission | Effect |
| -------------------- | ----------------------------------------------------------------------- |
| **Require approval** | Operators in this role must request approval before the action executes |
| **Approve** | Operators in this role can approve requests submitted by others |
| **Self Approve** | Operators in this role can approve their own requests |
Approval workflow configuration is available to admins in Project Settings → Roles. Operators cannot modify these settings.