Example policy setups

This page shows how organizations can combine policy rules with different conditions and outcomes to meet specific security goals. Each setup is built from the controls described in Rules — there’s nothing to install or request, and no preset to apply. Every setup below is a vault policy. The Block outcome isn’t available on the administrator policy, so organization-level operations such as user management always resolve to quorum.

​

How to read these setups

Each setup lists the rules in a policy in evaluation order. Anchorage Digital works down the list, applies the first rule that matches the operation, and resolves that rule’s outcome. A policy holds at most one conditional rule, and it always sits above the base rule for the same operation. See Conditional rules for how the two fit together, and Adding a conditional rule for the steps.

​

Restrict withdrawals to trusted destinations, block every other operation

Assets can only leave to an address your organization has already vetted and approved. Anything else is blocked before it reaches an approver. A withdrawal to a trusted address or to another vault on this policy matches the first rule and proceeds to quorum as normal. Every other vault operation falls through to the base rule and is blocked when you preview it. This turns your trusted destinations into a hard control rather than a convenience. Adding a trusted destination still requires quorum approval up front under your administrator policy, so the vetting step stays intact — see Trusted destinations. The outcome applies to the operation itself, not to where it started, so a withdrawal submitted through the API is rejected on the same terms as one started in the iOS app or web dashboard.

​

Require fewer approvals for vetted withdrawals

A higher number of quorum approvals still applies to a withdrawal heading somewhere new (or other operations), but movement between vaults using the same policy and to trusted destinations clears with just a single approval. Set the approval count on each rule to whatever suits your organization. The pattern is what matters: the conditional rule carries the lower threshold, and the base rule keeps your standard requirement for everything else. Sub-quorums work here too. You can require, for example, two approvals from a designated group on the base rule while the conditional rule stays at one — see Sub-quorums.

​

Limit vaults to one type of activity

A set of vaults set aside for a single purpose, such as staking, where no other operation can be initiated at all. The default Any vault operation rule covers every operation rule 1 doesn’t, and setting it to Block rejects them all. The rule above it re-opens the one operation the vault exists for, so staking proceeds to quorum while withdrawals, governance, and vault operations are all rejected. Assign this policy only to the vaults you intend to restrict. A policy applies to every vault it covers, so a policy shared with an active trading vault will lock that vault down too — see Vault policies.