History and controlled rollback
Screen 3.9 — restore a previous configuration as a new release, checked against current entitlements and rights.
PEEK Platform Administrator
/peek/customers/tenant-a/3-9Rollback never rewinds history. You select a prior configuration, compare it against current entitlement, policy and record rights, and stage it as a new version that references the old one. Intervening history is preserved.
3.9 · History & Controlled Rollback
Restore a previous configuration under current constraints. Open it at /peek/customers/tenant-a/3-9 (any tenant ID you can access works in place of tenant-a). The primary action is Stage rollback, which requires configuration.rollback.
How 3.9 works
1. Select prior configuration and compare it against current entitlement, policy and record rights
2. Stage a new release
Screen 3.9 contract
- Fields shown
- Version history, impact, current gates, approver
- Primary action
- Stage rollback
- Required capability
configuration.rollback- Validation
- Rollback cannot reinstate revoked rights, expired exceptions or unsupported contract versions.
- Successful outcome
- New version references the prior configuration and preserves intervening history.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.3.9.action(acceptance testAT-UI-3.9)- Requirements
- R02, R06, R07, R20, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-3.9
Related guides
Authorization, testing and publishing
Screens 3.5 and 3.8 — route agency authorization and PEEK technical review, run validation scenarios and publish an approved configuration.
Experience preview, release and rollback
Screens 7.7 and 7.8 — preview the agency experience with synthetic identities, then release or roll back platform components.