Governance presets
Three ways to run approvals that a small team can live with, replayed against your own history before you adopt one.
| Preset | What goes through | What still asks |
|---|---|---|
| Watch | Drafts (an inert artifact a person acts on) | Everything that changes a live setting |
| Assist | Drafts, plus reversible acts that narrow exposure | Anything that widens, silences, publishes or reaches a customer |
| Delegate | Assist, plus reversible acts that do not change exposure and classified acts whose derived direction is narrowing or neutral | Widening, silencing, publishing, customer-facing |
In every preset CRITICAL acts never get looser: where you have a CRITICAL rule it is raised to two people if it asked fewer, and where you have none the built-in refusal stays in force (a preset never turns a refusal into an ask). Merging stays human, and nothing lifts an invariant, an ask floor, a dual-control act or a human-only act. Review mode runs after all of them and cannot lift them either.
Adopting a preset
- Settings > Approval policies > Governance presets > pick a preset and run the replay. It shows the last 30 days of your requests: what would have been allowed, asked or denied, per area, with the undo for everything allowed. With little history it shows a fixed scenario set instead.
- Request it.
policy_preset.applyis CRITICAL, human-only (org:admin) and dual control: a second person and a security-key confirmation are needed, and the request carries the replay you saw (a changed history or policy table voids it). - It runs in shadow for 7 days: nothing changes. Then it is enforced: rows are created or tightened and each change is journalled. Enforcement only writes rows the approved plan contained: if the plan would now create anything else (you deleted a rule during the week, or a new act appeared), nothing is written, the application is cancelled with a recorded reason, and you replay and apply again.
- To undo, request the restore: a preset in shadow is cancelled, an enforced one is rolled back row by row (a row you edited since is left and named).
Your own floors survive: a conditioned row (for example "never auto-apply in production"), a DENY, a tagged row or a row named for an act keeps that act asking. A preset only ever tightens a row of yours.
Your decision windows
Each approver sets their own times (for example 09:30 and 16:00), quiet hours and a daily cap (15 by default). No tool reaches these. With nothing set, asks reach you at once.
For asks from agents, services and OAuth clients: if every eligible approver is outside a window, the ask waits for the first window (paging waits, deciding does not) and arrives with the others as one ranked bundle. Urgent asks (CRITICAL, dual-control, a narrowing act on an issue with 100 or more users, a change judged regressed in the last day) are always sent at once. Past every approver's cap, an ask is not filed: the agent gets APPROVAL_DEFERRED_TO_DRAFT and a "would have asked" receipt is recorded. Agents see deferredUntil, their place in the held line and the asks left today in decision_preview and approvals_list.