Help users toLeave a service
Also known as: sign out
Allow users to leave a service at the right time.
Signing out from the header
This pattern is more likely to be used on multi-use and caseworking services. Signing out of a service is best practice - for example, for internal services where users share a workspace.
This pattern is used by:
- Entity search
- Booking returns and movement
Leaving a service inline
This pattern is more likely to be used when a user is working from a public space and is inputting sensitive data.
You should do research to find out at what point a user will need to leave your service. An option should be provided with a persistent link through as well as the end of the service.
This pattern is used by:
- Apply for the EU settlement scheme
- Update your EU settlement scheme details
- Employer checking service
How it works
For public-facing services it may be better to describe it as leaving a service rather then signing out. Users might not feel they have signed in to a service.
Only give users the option to leave mid-service if they can save progress and carry on with the service at another time.
After leaving the service, take users to a confirmation page that includes:
- a confirmation that the sign out or leaving a service has been successful
- the option to sign back or return to the service again
Accessibility
If your service uses this pattern, let us know of any insights you have on accessibility considerations.
Research
Users are confident in using a 'leave the service' button at the end of a transaction. Users mention they want to make sure they leave a service securely.
Help us improve this pattern
This pattern needs improving. We need evidence about:
- how to write for this pattern
To contribute, add your thoughts and research findings to our GitHub discussion, or follow our contribute guidance.