What is Forced single sign-on (SSO)?


***Currently, Forced SSO is in beta. If you want to enable Forced SSO on your org, please reach out to your CSM***

What is single sign-on (SSO)?

Single sign-on is a technology that combines several different login screens into one. It's convenient for users and more secure for companies. 

At Alyce, we allow our customers to login through SSO using MS Office of Google. 



Instead of logging into Google, Evernote, Jira, and Alyce, wouldn’t it be nice to log into one application and then have access to your others?

That’s what single sign-on (SSO) allows users to do on many SaaS applications. It’s super convenient for users who no longer need to remember several credentials every time they need to log into an application. 

It’s quick, convenient, and removes the likelihood of needing to recover passwords. 


Forced SSO is also considered to be more secure. It’s much easier for IT teams to ensure better password policies (like periodic resets), enable multi factor authentication, and enforce password re-entry when a certain time passes. 

Because of the single point credential management.

SSO vs Forced SSO

What is the difference?

With SSO we allow end users to choose between creating a password and using Single Sign On. With Forced SSO, users are unable to create a password, they need to use SSO in order to access the app.



SSO is shown on the top part of this login screen, where you can click to sign in with Google or MS Office. 

0 out of 0 found this helpful



Please sign in to leave a comment.