Business Accounts are in early access. See Business Accounts for the model.
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. For example, with an Account value cap of 100 USDC and a Wallet value cap of 50 USDC, a 75 USDC payment is above the wallet cap, so the stricter cap applies. A request that a layer rejects is never signed. If the wallet also requires approvals, a rejected request never becomes an approval proposal either, and Approvals describes the order of the checks.
The Account layer is the only layer that exists just for business accounts, and it covers only the wallets in a business account. The Wallet and Signer layers are in early access.
A signer can edit or remove the rules on their own signer layer. For a rule that someone else created, such as one an admin set, the signer can make changes only when the rule is marked
modifiableBySigner. Even then, the signer can change only constraint fields, such as addresses and value limits, and cannot change the rule type or the security settings, such as Blockaid checks or export blocking.
See Policy Layers for how the layers combine and how a signer can be allowed to modify a rule.
What a rule can do
Each rule below can be set on the Account, Wallet or Signer layer.
The approval rule is a quorum policy. It depends on the account’s members and roles, so it only makes sense for business accounts.