Open sarawilcox opened 1 year ago
We're about to test a new version of this screen with slightly different content and a warning popup, but this is the timeout screen we're using in our service at the moment.
The NHS e-Referral Service has some documentation on how they handle session time limits:
An absolute timeout occurs when the user has been logged on to e-RS for 8 hours.
10 minutes before the 8 hours expires, a notification box, will be displayed with a countdown.
If the user does not save their work before the time elapses their changes will be lost when the user is automatically logged out of e-RS.
The message below will appear when the time elapses and automatically logs the user out.
An idle timeout occurs when a user has not carried out any interaction with e-RS.
After being idle for 10 minutes, a notification box will be displayed with a countdown.
If no action is taken within the time window the user will be logged out of e-RS.
The message will appear when the time elapses and automatically logs the user out.
What
Warn users that their session is about to time out and let them extend it if possible.
Why
All services that use sessions already use, or should use this pattern.
GOV.UK examples and guidance
Note GDS recommends a 20 to 30 mins timeout.
If you have any NHS examples, please add screenshots, UR findings, design thinking etc.