Skip to main content
Some funds require more than one person to move them. Whether you’re managing treasury reserves, holding funds on behalf of clients, or simply want a check on large outflows, PrimeVault lets you configure a vault that requires multiple independent parties to approve before any transaction executes.

​
When to use this

This setup is ideal when you need separation of duties. For example, an internal treasury officer plus an external auditor, or a custodian holding approval rights as a neutral party. No single person can move funds alone. Image Step 1: Create a Policy Template Go to Policy Templates and start a new template. Give it a name that reflects its purpose (e.g. “High-Value Treasury Vault”). Image Step 2: Add your signers as Vault Owners Under Add Owners, add the specific users whose approval you want to require along with any other users as well. Viewers can see all vault balances, pending transactions, and transaction history - but cannot create or approve transactions. Be deliberate about who you add as a Viewer, especially for sensitive treasury vaults. Only grant viewer access to parties who have a legitimate need for read-only visibility. Step 3: Set the Transfer Limit Policy Under Policies → Transfer Limit, configure:
  • Spend limit: Set to $0 if you want every transaction to require approval, or a threshold (e.g. $10,000) if smaller transactions can flow freely
  • Action: Select Additional Approvals
  • Number of approvals: Set this to match how many of your signers must approve. For a 2-party setup (e.g. escrow + auditor), set this to 2
Image Step 4: Apply to your Vault Complete the template setup and apply it to the relevant vault. From this point, any transaction that hits the threshold will be held pending until all required parties have signed off in PrimeVault.

​
Conditional Approval Rules via Custom Transfer Policy

For more granular control, you can create a custom transfer policy that applies different approval requirements based on who initiates the transaction rather than applying a single rule to all vault activity. To set this up, click Add Custom Transfer Policy on the vault’s policy settings page. From there, you can designate specific vault owners as the transaction creators the rule applies to. When any of those owners initiates a transfer, the policy triggers the configured action. Image For example, to require two additional sign-offs whenever a junior operator sends a transaction: select that operator under Vault Owners, set Additional Approvals to 2, and save. The two approvals must come from other owners on the vault and the creator’s own action is excluded from the count. Image This is useful when different team members carry different risk profiles, and a one-size-fits-all quorum doesn’t reflect your actual authorization structure.

​
Policy Setup Notes

The approval count applies to all users in the Vault Owners list. If you add 5 users and require 3 approvals, any 3 of those 5 can approve. Add only the users who must approve every transaction. For this setup, that means 3 users: one from your org, your escrow party, and your auditor.