Add an external approver
Add a wallet to a vault's approver set so it can co-sign spends above the approval threshold.
What you need
- An existing vault, owned by your connected wallet.
- The approver's wallet address or public key — a wallet you or a trusted co-signer controls, separate from any agent key on the vault.
- A decision on the approval threshold: how many of the configured approvers must sign, and above what amount.
Steps
- From the vault's approver configuration, add the new approver's address. Vaults support a bounded number of approver slots (multiple independent approvers can be configured), and this is an owner-signed covenant operation — only the owner can add, remove, or change approvers.
- Set (or confirm) the M-of-N threshold — for example, "2 of 3 approvers must sign" — and the amount above which it applies.
- Review and sign. Once confirmed on-chain, the new approver's key is part of the vault's covenant-committed approver set.
- Communicate to the approver, out of band, how they will see and act on pending requests — typically by connecting their wallet to the same PolicyVault deployment (self-hosted or hosted) and viewing requests awaiting their approval.
What the approver can do afterward
Exactly one thing: sign approvals for specific spend requests that qualify under the threshold, on this vault. See External approver for the precise, narrow scope of this role — an approver never gains the ability to spend, to change policy, or to act as the owner.
Removing an approver
Removing an approver (or changing the threshold) is also an owner-signed covenant operation, following the same pattern as adding one. A removed approver's prior approvals on already-consumed requests are not affected retroactively, but it can no longer approve new requests.
See also: Require approvals, Approval threshold, Approval not visible if an approver reports not seeing a pending request.