Operations that don’t need your CEO’s signature
Run routine treasury operations on scoped, onchain permissions — no signing ceremony, no standing risk to the whole treasury.
Every routine treasury action turns into a multi-signer ceremony, because the only available trust unit is “can sign anything.” So either operations stall while you chase signatures, or you widen access and every operator effectively holds the keys to the entire treasury.
The questions that actually matter
Blast radius
What’s at risk when an operator’s laptop is compromised? When a misclick goes wrong? Today the answer is "the whole treasury." It shouldn’t be.
Coordination cost
How many people are in the loop for a weekly rebalance? If the answer involves chasing signatures across timezones, your operations aren’t scaling.
Audit trail
Can your auditor verify every action against a rule, without taking your word for it?
Reach
Treasury rarely fits in one venue. Adding Aave, Morpho, or a new chain should be a permission edit — not a vendor integration cycle.
On the chain. By the chain.
Scoped roles, enforced onchain
A Treasurer role that can rebalance stables up to a cap. A Payroll role with an allowlist of recipients. A Yield role bounded to whitelisted protocols. Out-of-bound calls revert.
No quorum for routine work
Routine actions run under scoped roles. Full-quorum signing is reserved for the decisions that genuinely need it.
Auditor-readable controls
Roles are smart contracts. Your auditor reads the contract. Anyone can query the chain. No Notion doc; no "trust us."
New venues as permission edits
Adding Morpho is specifying which Morpho contracts and methods are allowed. Hours, not weeks.
One role: rebalance stables, up to $50k a week
Your treasury holds USDC and ETH. You want a Treasurer role to rebalance between stables (USDC, DAI, USDS) up to $50,000 per week, no leverage, no withdrawals.
In Zodiac you set those swap permissions up in the UI — the stablecoin allowlist with a $50k weekly allowance — and assign the Treasurer role to the operating team member who runs rebalances. They can act freely within the bound; the chain refuses everything else.
When governance approves expanding the role to include staking, the permission update goes through review under full quorum before it takes effect.