Published
A shared sign-in can simplify access to several applications. Behind that familiar login screen are separate decisions about identity, permission and responsibility.
Know who is signing in
An account identifies a user to the connected services. The account lifecycle includes registration, recovery and changes to the information associated with that user. These operations deserve the same attention as the initial login.
Decide what each role can do
An applicant can submit a request; a reviewer may assess it; an administrator manages a different set of tasks. The same identity system can serve all three, while each application enforces the permissions relevant to its work.
Prepare for change
People move between roles and leave organisations. A shared sign-in project should explain who approves access changes and how those changes reach connected applications. Clear administration is part of the product experience.
Map the applications first
An inventory of services, user groups and application owners is a useful first step. Explore Authentic8 to begin a discussion about participating services and the sign-in journey.