It does save time, but I do not believe saving time would be the motivator to implement it. Not having to save as many passwords in a separate solution for each platform/website reduces the security risks dramatically and improves the experience for the users.
Adding two-factor authentication would be easier as it would apply to your primary account only and you can use a single authenticator token for that (potentially).
You can use SSO for the majority of the platforms but perhaps segregate certain environments from it if need be or simply ensure that permissions are set correctly for those using SSO - in general, is definitely the better way of handling authentication going forward.
Search for a product comparison in Single Sign-On (SSO)
SSO not only saves time but also keeps the environment more secure.
Many start-ups tend to avoid implementing SSO for various reasons, so employees end up juggling between 7-10 different websites and deal with just as many logins to accomplish their tasks.
The browser plug-ins of various password storing solutions don't always work and sometimes glitch out to a point, where you want to turn them off or not use them at all.
What this could lead to is weaker, more human passwords and more importantly, reuse of it. Having SSO just makes things so much more fluid and out of the personal experience, more engaged and productive.
Because of the very nature of how SSO works, it is quite obvious that it saves time. With SSO only requiring users to provide one set of login credentials, one time, to access multiple sessions in different applications, that in and of itself saves time. By providing a single point of access, an SSO not only reduces wasted time, but reduces extra resources. Whatsmore, users with just one password to access all their apps don’t require assistance as often, saving time on support calls and making employees less reliant on IT teams. I think the biggest benefit of implementing an SSO solution is that systems remain secure - whether users are working in the office or from a remote location.
While it is hard to quantify “how much time” is saved by using an SSO, I imagine that since there’s no need to hop between multiple login URLs, or reset passwords, users save between 5 to 15 seconds per login. Another factor to consider is how entering login credentials can consume time. Entering passwords for multiple apps multiple times during a work shift can be time-consuming. Depending on a company’s policies around password security, I would estimate that the login process can take anywhere between 30 and 90 seconds. During this time, it is not unlikely for an employee’s frustration level to rise while their productivity level drops.
The added benefits of having an SSO also help save time. For example, with saved credentials, users' average login time decreases since they do not have to manually enter their username and password information every time. By logging in only once, the user saves additional time, rather than having to sign in every time they return to a session they had previously started. Furthermore, having to login one time is especially helpful when devices typically time out, or lock you out due to inactivity during a session. When an SSO solution is in place, there is a bigger reduction in time since users do not have to re-authenticate their identity after time away from their device.
With an SSO, the number of times a user has to enter a password is minimized. Thus, it reduces the likelihood that they will accidentally lock their account and need to call the help desk. As you probably already know, resetting a password can be a hassle, causing you to go through a verification and authentication process, which is also timely.
Moreover, if a user is trying to login on the small screen of a mobile device, they are prone to entering usernames and passwords incorrectly, which can result in either a longer login time or a call to the helpdesk. By using an SSO and reducing the number of logins (without compromising security), it can help save additional time by minimizing the helpdesk issues related to the end user’s credentials.
In summary, an effective SSO solution can not only save your organization a lot of time, but it can also help you achieve significant cost savings which otherwise might not be possible without an SSO system. Besides saving time, deploying an SSO solution comes with other benefits for your organization, since it is an effective way to boost employee satisfaction and productivity as well.
- at a tech services company with 51-200 employees
Real User
Mar 9, 2022
The more you have applications protected by SSO, the more you can save time.
The more your usual login experience is complex (long login name, long and complex password to enter from a smartphone keyboard, unfriendly second authentication factor), the more you can save time.
Also, the end user experience is slightly different if you run a survey before and after SSO implementation about the feeling, about the time spent to log in and if you measure the time to log in based on systems and application logs.
Single Sign-On (SSO) simplifies user management by allowing users to access multiple applications with one set of credentials, enhancing security and user experience.SSO solutions are designed for easing credential management and improving security. They help organizations streamline user access to a wide range of applications with one set of credentials. This reduces login friction, increases security, and supports compliance requirements. Users save time and IT teams benefit from fewer...
It does save time, but I do not believe saving time would be the motivator to implement it. Not having to save as many passwords in a separate solution for each platform/website reduces the security risks dramatically and improves the experience for the users.
Adding two-factor authentication would be easier as it would apply to your primary account only and you can use a single authenticator token for that (potentially).
You can use SSO for the majority of the platforms but perhaps segregate certain environments from it if need be or simply ensure that permissions are set correctly for those using SSO - in general, is definitely the better way of handling authentication going forward.
SSO not only saves time but also keeps the environment more secure.
Many start-ups tend to avoid implementing SSO for various reasons, so employees end up juggling between 7-10 different websites and deal with just as many logins to accomplish their tasks.
The browser plug-ins of various password storing solutions don't always work and sometimes glitch out to a point, where you want to turn them off or not use them at all.
What this could lead to is weaker, more human passwords and more importantly, reuse of it. Having SSO just makes things so much more fluid and out of the personal experience, more engaged and productive.
Because of the very nature of how SSO works, it is quite obvious that it saves time. With SSO only requiring users to provide one set of login credentials, one time, to access multiple sessions in different applications, that in and of itself saves time. By providing a single point of access, an SSO not only reduces wasted time, but reduces extra resources. Whatsmore, users with just one password to access all their apps don’t require assistance as often, saving time on support calls and making employees less reliant on IT teams. I think the biggest benefit of implementing an SSO solution is that systems remain secure - whether users are working in the office or from a remote location.
While it is hard to quantify “how much time” is saved by using an SSO, I imagine that since there’s no need to hop between multiple login URLs, or reset passwords, users save between 5 to 15 seconds per login. Another factor to consider is how entering login credentials can consume time. Entering passwords for multiple apps multiple times during a work shift can be time-consuming. Depending on a company’s policies around password security, I would estimate that the login process can take anywhere between 30 and 90 seconds. During this time, it is not unlikely for an employee’s frustration level to rise while their productivity level drops.
The added benefits of having an SSO also help save time. For example, with saved credentials, users' average login time decreases since they do not have to manually enter their username and password information every time. By logging in only once, the user saves additional time, rather than having to sign in every time they return to a session they had previously started. Furthermore, having to login one time is especially helpful when devices typically time out, or lock you out due to inactivity during a session. When an SSO solution is in place, there is a bigger reduction in time since users do not have to re-authenticate their identity after time away from their device.
With an SSO, the number of times a user has to enter a password is minimized. Thus, it reduces the likelihood that they will accidentally lock their account and need to call the help desk. As you probably already know, resetting a password can be a hassle, causing you to go through a verification and authentication process, which is also timely.
Moreover, if a user is trying to login on the small screen of a mobile device, they are prone to entering usernames and passwords incorrectly, which can result in either a longer login time or a call to the helpdesk. By using an SSO and reducing the number of logins (without compromising security), it can help save additional time by minimizing the helpdesk issues related to the end user’s credentials.
In summary, an effective SSO solution can not only save your organization a lot of time, but it can also help you achieve significant cost savings which otherwise might not be possible without an SSO system. Besides saving time, deploying an SSO solution comes with other benefits for your organization, since it is an effective way to boost employee satisfaction and productivity as well.
The more you have applications protected by SSO, the more you can save time.
The more your usual login experience is complex (long login name, long and complex password to enter from a smartphone keyboard, unfriendly second authentication factor), the more you can save time.
Also, the end user experience is slightly different if you run a survey before and after SSO implementation about the feeling, about the time spent to log in and if you measure the time to log in based on systems and application logs.
So, there is no unique truth to your answer.