Approval tiers
Decide which actions auto-close, which need a checkpoint, and which must stop for explicit review.
Use this page when
Read this page when you are setting the first review policy for a workspace or tuning an existing approval model.
Tier model
| Tier | Expected closure |
|---|---|
| Low risk | policy evaluates and auto-allows |
| Medium risk | app confirm or lightweight human checkpoint |
| High risk | explicit reviewer action before closure |
Start with these decisions
- which actions are safe enough to auto-close
- which actions need a visible checkpoint
- which actions must never close without explicit review
- which receipts need to be reusable in buyer review later
Recommended rollout
- Prove one low-risk path and confirm the receipt closes cleanly.
- Add one medium-risk path and make sure the checkpoint is visible.
- Add one high-risk path and confirm the queue is explicit.
- Expand only after those three paths are understandable.
What success looks like
A good tier model leaves you with a usable low-risk path on day one and a clearly explained queue for higher-risk work.
Common mistakes
- everything auto-closes, so the model is too permissive
- everything queues, so day-one usage becomes unusable
- the receipt never explains which tier drove the decision