Inside an application, mid-work
The frame below stands in for Operation Solid Rock after an SSO login - the application's own session (revocation layer ③) is what ends here.
Viewing as Thiri Demo (MOD-P-0900001). Switching personas changes this screen.
Demo controlsTwo ways the session can end, triggered on demand. In the product, layer ③ ends it, not a button.
Design note
Entry decision (simulated):ALLOWELIGIBLEEligibility present and tier conditions met.
Operation Solid Rock(mock frame)Simulated application
Unsaved changes
Synthetic canvas: a record mid-edit, abstracted. No data here, not even fake data.
Design note
Why two designs, not one
A routine expiry is the system working as designed: the message offers a way back and implies no fault. A compromise suspension must not offer a way back - the person holding the session may not be the account holder. If both endings render the same screen, one of those two audiences is being told the wrong thing.