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

# Approval - Approval Requests

> Request and track approvals from users via Slack, Teams, or email

## Overview

The Approval step sends an approval request to one or more people and pauses the flow until they respond.

## Use When

* You need a human sign-off before the flow continues (budget approval, contract terms, policy exceptions)
* You want the request delivered somewhere specific — Slack, Teams, or email

## Configuration

* **Content to approve** — add content from recent steps or other flow elements for the approver to review
* **Select Approvers** — click **Add group** to choose who needs to approve; you can add more than one group
* **Add condition group** (per approver group) — makes that group's approval requirement conditional, e.g. "Request approval if Contract Value Greater 100000." This is how you route to different approvers based on flow data (a \$100K+ deal to a VP, everything else to a department manager) inside a single Approval step.
* **Approve by order** — toggle on to require approvals in the order the approver groups were added; off means order doesn't matter
* **Select channel** — **Slack**, **Teams**, or **Email**
* **Recipients / Subject / Message** (Email channel) — the message body supports inserting flow content with "@"
* **Enable reminders** — automatically remind approvers who haven't responded

<Tip>
  There is no separate approval-logic setting for unanimous vs. any-one-approver vs. majority — **Approve by order** is the only sequencing control, and per-group conditions are the only way to make approvers vary by data. There's also no built-in timeout/escalation field or rejection-routing configuration on this step; if you need different paths for approved vs. rejected, follow the Approval step with a [Condition](/features/flows/condition) step that checks the result.
</Tip>

## Related Components

<CardGroup cols={2}>
  <Card title="Condition" icon="code-branch" href="/features/flows/condition">
    Route differently depending on the approval outcome
  </Card>

  <Card title="Notify" icon="bell" href="/features/flows/notify">
    Tell other stakeholders once a decision is made
  </Card>

  <Card title="Sign" icon="signature" href="/features/flows/sign">
    Send for signature after approval
  </Card>
</CardGroup>