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

# Collect approvals

<Info>
  Manual Approvals is an Enterprise feature. Reach out to [sales@privy.io](mailto:sales@privy.io) to
  request access.
</Info>

To require approval from the assigned quorum of reviewers before a treasury operation (transfers, configuration changes, and signatures) executes, you will need to enable Manual Approvals.

All approvals are secured by biometric and/or TOTP MFA. No transaction can execute without the
required number of authenticated approvals.

<Card title="Manual approvals documentation" icon="book" href="/controls/dashboard/overview">
  Full guide to setting up reviewer groups, proposing intents, and understanding intent lifecycle
  and statuses.
</Card>

## Approval workflow

At a high level, Treasury Management follows a **propose → review → approve** flow:

<Steps>
  <Step title="Propose an intent">
    A team member [initiates a transfer](/treasury-management/transfers), signature, or
    configuration change via the Treasury Management workspace or API. This creates a pending
    intent.
  </Step>

  <Step title="Review the intent">
    Team members in the assigned quorum [review the pending intent](/controls/dashboard/approvals)
    on the Approvals page. Each reviewer inspects the details — recipient, amount, chain, and any
    relevant context.
  </Step>

  <Step title="Approve or reject">
    Reviewers authorize or reject the intent using MFA-secured approval. Once the quorum threshold
    is met (e.g., 2-of-3 approval), the transaction executes automatically.
  </Step>
</Steps>

## Related resources

<CardGroup cols={2}>
  <Card title="Key quorum setup" icon="users" href="/treasury-management/setup#creating-a-key-quorum">
    Create and manage approval groups
  </Card>

  <Card title="Policies" icon="shield" href="/treasury-management/setup#5-add-policies-optional">
    Configure enforceable transaction guardrails
  </Card>
</CardGroup>
