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

# Example Rule: Transfer Policy

Seeing a rule in action is the fastest way to understand how the Policy Engine works. This example walks you through a complete transfer rule, from setup to approval logic, so you can build your own with confidence.

![Image](https://mintcdn.com/primevaulthelp/v4SUV77yWZrcZbOp/images/image-69.png?fit=max\&auto=format\&n=v4SUV77yWZrcZbOp\&q=85\&s=72bed20c29f95d62fae97c7f679f917e)

## Rule Configuration

A Transfer rule governs onchain asset movements from your vaults to a destination. In this example, the rule allows AAVE transfers from All Core Vaults to Test Vault Group 1, with approvals that scale based on transaction size.

| Field | Example Value | Notes |
| - | - | - |
| Rule Name | Internal Transfer Policy | Choose a name that reflects the scope of the rule. |
| Vaults | All Core Vaults | Using a Vault Group means any new vault added to the group is automatically covered. |
| Action | Transfer | This rule applies to onchain asset transfers only. |
| Creators | Shriya | Only the listed creators can initiate transactions under this rule. |
| Signers | Vivek Kumar, Jay McCarthy, test-ec2-user | The pool of users ELIGIBLE to approve. Who must sign is defined in Frequency Actions. |
| Counterparty | Test Vault Group 1 | Transfers are only permitted to destinations within this group. |
| Asset | AAVE | Leave blank to apply the rule to all assets. |
| Chain | Base Testnet | Leave blank to apply the rule across all chains. |
| Spend Denomination | Native | Limits are in AAVE units. Set to Fiat to use USD equivalent instead. |

> [!TIP]
>
> **Tip:** Counterparties can be **internal vault groups or external addresses**. If you are sending to external destinations, consider applying stricter approval requirements to reflect the higher risk.

## Frequency Actions (Per Transaction)

Each transaction is checked against the tiers below. If your transaction amount is less than or equal to a tier's Max Amount, that tier's rules apply.

| Tier | Action Type | Min Amount | Approval Count | Mandatory Approver |
| - | - | - | - | - |
| 1 | Additional Approval | 1,000 AAVE | 1 | Vivek Kumar |
| 2 | Block | 10,000 AAVE | - | - |

## Outcome

| Amount | What happens |
| - | - |
| 0 - 1,000 AAVE | Creator signature only. Transaction proceeds immediately. |
| 1,001 - 10,000 AAVE | Creator + Vivek Kumar must approve before the transaction proceeds. |
| Over 10,000 AAVE | Automatically blocked. No approvals can override this. |

![Image](https://mintcdn.com/primevaulthelp/v4SUV77yWZrcZbOp/images/image-70.png?fit=max\&auto=format\&n=v4SUV77yWZrcZbOp\&q=85\&s=1f0885f4044e1699c1af7b6bee2d8830)

This is how a single rule can handle the full range of transaction sizes, from instant approvals to hard blocks.


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