Policies

How the policy layers apply to business-account wallets and who can edit each one.

Business Accounts are in early access. See Business Accounts for the model.

Members and signers decide who can act, and policies decide what they are allowed to do. A business-account wallet uses the same policy engine as any Dynamic embedded wallet, described in Policies & Rules, and a business account adds one more layer on top.

Layers

Rules are evaluated in layers from the broadest to the narrowest, and a request must pass every layer that applies. Rules combine by tightening: a narrower layer can only make a rule stricter, never loosen a rule set at a broader layer.

Layer	Applies to	Who can edit it
Environment	Every wallet in the environment.	The developer, through the dashboard or API.
Account	Every wallet in the business account.	A business-account owner or admin.
Wallet	One wallet.	A business-account owner or admin.
Signer	One signer on one wallet.	The signer for their own layer, or a business-account owner or admin for any signer.

See Policy Layers for how the layers combine and how a signer can be allowed to modify a rule.

What a rule can do

A rule can restrict the addresses a wallet may interact with, cap the value of a single transaction, block private key export, or require approvals before the wallet signs. The approval rule is a quorum policy, and it is the rule type that only makes sense for business accounts because it depends on the account’s members and roles.

How policies differ from governance

Policies limit what a wallet can sign. Approvals limit which changes to the account can apply, such as adding a member or linking a wallet.

Next steps

Pick your SDK under Implement in the sidebar to set policies on an account, wallet, or signer.