Approval flow
Check how OSuite closes low-risk, medium-risk, and high-risk decisions, and what an approval receipt must explain.
Use this page when
Use this page after the first governed decision reaches OSuite and you need to confirm whether approval behaves the way you expect.
How approval closes
- Auto allow handles low-risk decisions after policy evaluation.
- App confirm inserts a lightweight human confirmation step for medium-risk actions.
- Approval queue pauses high-risk actions until an explicit reviewer decision is recorded.
What to verify
Check these points on the first real review path:
- low-risk decisions really auto-close
- medium-risk decisions surface a visible confirmation step
- high-risk decisions enter a review queue instead of silently failing
- the receipt explains who decided, what they decided, and under which conditions
What an approval receipt should contain
- reviewer identity
- decision outcome
- reason or policy basis
- attached conditions or constraints
Common approval failures
| Problem | Likely cause | Where to go |
|---|---|---|
| Expected review never appeared | action tier or approval flag is too low | Troubleshooting |
| Receipt exists but explanation is weak | review metadata is incomplete | Artifacts and fields |
| Buyer story still feels unclear | the authority model has not been read yet | PCAA |