Policy exceptions and expiration
Screen 3.7 — review bounded exceptions with explicit scope, authority and end date.
PEEK Technical Reviewer
/peek/customers/tenant-a/3-7 Live walkthrough · Policy exceptions and expiration
An exception is a time-boxed variance within a delegable boundary. When it expires the restrictive effective value resumes automatically and affected work is reevaluated. Exceptions cannot be backdated, extended indefinitely or used after expiry.
3.7 · Policy Exceptions & Expiration
Manage bounded exceptions and their expiry. Open it at /peek/customers/tenant-a/3-7 (any tenant ID you can access works in place of tenant-a). The primary action is Review and schedule exception, which requires exception.review.
How 3.7 works
1. Review a requested variance, permitted override scope, authority and expiry
2. Publish only within the delegable boundary
Screen 3.7 contract
- Fields shown
- Requested variance, allowed override scope, approver, end date
- Primary action
- Review and schedule exception
- Required capability
exception.review- Validation
- No exception may bypass isolation or a nondelegable deny. Start/end and renewal require explicit authority.
- Successful outcome
- At expiry the restrictive effective value resumes; affected work is reevaluated.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.3.7.action(acceptance testAT-UI-3.7)- Requirements
- R02, R06, R07, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-3.7
Boundary — No exception can bypass tenant isolation, prohibited data access or a nondelegable control.
Rejected even if the browser allows it — Backdate, indefinitely extend or use an expired exception to process new data; deny it.