> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/getting-setup/approvals-feature-guide.md).
# Approvals feature guide
## Overview
The Approvals feature allows you to create custom approval rules for crypto withdrawals and bank withdrawal requests made through your business account. By setting up approval rules, you can ensure that transactions require review and authorization from designated team members before they're processed.
## Creating Approval Rules
To create an approval rule, navigate to **Approvals → Rules** and follow these steps:
{% hint style="info" %}
Only users with the [Owner role](/getting-setup/back-office-user-roles.md) can create approval rules. You can create one rule per scope — one for Crypto Payouts and one for Bank Withdrawals.
{% endhint %}
### 1. Choose Your Rule Scope
Select which type of transactions this rule will apply to:
**Crypto Payouts** — This scope covers:
* Creating payouts from crypto accounts
* Creating mass payouts via CSV upload
* Creating payout payment links
**Bank Withdrawals** — This scope covers:
* Bank withdrawal requests only
{% hint style="warning" %}
**Approval rules apply to dashboard-initiated transactions only.** Crypto payouts and bank withdrawals created via the API using an API key are processed without requiring approval, even if a matching rule is active.
{% endhint %}
### 2. Set Required Approvals
Specify the minimum number of approvals needed for each transaction request that falls under this rule.
### 3. Designate Approvers
Select which users are authorized to approve or reject transaction requests under this rule.
### 4. Self-Approval Settings
Decide whether transaction initiators can approve their own requests. By default, this option is disabled, meaning initiators cannot approve their own transactions.
Creating a new approval rule
## How Approvals Work
Once an approval rule is active:
**For Transaction Initiators:**
* Any transaction request you create that matches a rule will require the specified number of approvals before processing
* You can view the status of your requests on the **Approvals → Requests** page
* You can cancel your own request at any time (even if you can't approve it)
* If you're allowed to approve your own requests, you can both approve and cancel them
* You'll receive email notifications when your request is approved or rejected
**For Approvers:**
* You'll receive email notifications when a transaction requires your review
* All pending approval requests are visible on the **Approvals → Requests** page
* You can either approve or reject the request
* If even one rejection is received, the transaction request is canceled completely
* The transaction will only proceed once the required number of approvals is reached
## Managing Approval Rules
### Deleting Rules
Only users with the Owner role can initiate rule deletion. When you delete an approval rule, it enters a 24-hour cooling-off period before being permanently removed. This safeguard helps prevent accidental deletions.
**Important:** If you delete a rule while transaction requests are still pending approval, those requests will still need to be resolved (approved, rejected, or canceled) according to the original rule requirements.
The rule is set for deletion
For questions about setting up approval rules or managing transaction approvals, contact support at .
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.txn.io/getting-setup/approvals-feature-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.