Policies & compliance
Every product has a Policies page where an owner (or anyone with Publish on policies) builds rules that apply automatically to every transaction. A policy is a set of rules; each rule either blocks the action outright, flags it, or routes it to compliance review.
Cross-product policies live in Treasury
Each product's Policies page manages rules for that product. Policies that span several products — an org-wide daily limit, for instance — are created and edited in Treasury.
Common rule types
| Rule | What it does |
|---|---|
| Amount limit | Block, flag, or send to compliance any single transaction above a USD amount |
| Daily limit | Cap total USD moved per day, org-wide or per user |
| Required approvals | Above a USD threshold, require sign-off from named approvers before execution |
| Working hours | Restrict when transactions can be submitted, by day and hour range |
| Whitelist / blacklist | Only allow (or block) specific addresses — pairs well with the address book |
| Country restriction | Block transactions associated with specific countries |
| Risk threshold | Flag or send to compliance anything above a USD amount for extra review |
Product-specific rules
Trade adds rules for trading pairs, order types, and max slippage; Earn and Borrow add rules that restrict which protocols or assets can be used. These layer on top of the common rules above.
Compliance holds
When a rule's action is "compliance" rather than "block," the transaction pauses and appears on the Compliance page for review instead of failing outright. A compliance reviewer can clear it to proceed or reject it.
Reporting and audit
Every product has a Reports page for exporting transaction and approval history — useful for audits and reconciling with your existing finance tooling. Treasury additionally keeps the org-wide audit log (Treasury → Audit Logs): every mutating action across the platform, recorded with who, what, and when.