Continuity Access Detail
A specific restriction window showing why continuity access was preserved, what deadlines are still live, and what must happen before full revocation can complete.
Restriction detail should anchor one continuity case rather than collapsing everything into a generic queue row.
The detail page must make the real continuity burden visible before any further restriction is approved.
The operator should see exactly what is endangered if access is not restored in time.
That keeps revocation decisions tied to real deadlines instead of abstract policy language.
That turns continuity into a real operating safeguard, not a hidden footnote.
{
"restriction_window_id": "jordan_lee_restriction_window",
"employee_id": "emp_jordan_lee",
"restricted_at": "2026-03-12T08:42:00Z",
"continuity_access": true,
"proof_windows_at_risk": 1,
"restore_required_by": "2026-03-15T16:00:00Z"
}Restriction detail should connect the access change to the commitments it still affects.
The employee retains the minimum required access because active commitments still exist.
Restriction timing matters because it frames the restore window and audit trail.
The operator responsible for the restore should be visible from the first screen.
This employee still has four live commitments that justify continuity protection.
One proof path still depends on timely restore or continued protected access.
The deadline for safe restoration should stay visible and auditable.
The employee still has the minimum market and proof access required to finish active commitments.
The restore window is tightening and should stay visible to the organization owner.
Only one proof path is currently at risk, but that is enough to require active monitoring.
Broader organization access was reduced while continuity protection remained active.
The employee kept active-market access, reminders, and proof eligibility.
Full continuity risk increases if the organization has not restored the account by this point.
The detail surface should show the current access reduction, the reason that triggered it, and the exact active commitments that still require continuity protection.
That keeps revocation decisions tied to real deadlines instead of abstract policy language.
A continuity detail page should make the next restore checkpoint obvious and show how the organization record will be affected if access is not restored in time.
That turns continuity into a real operating safeguard, not a hidden footnote.