Single Sign-On
Requiring SSOEnterprise
Turning off password and social sign-in for the domain, so everyone signs in through the identity provider.
Requiring SSO makes the identity provider the only way people of the email domain sign in. With Require SSO for everyone turned on, password sign-in and social sign-in, such as Google or GitHub, are turned off for every email in the domain, so the company's sign-in policies, such as multi-factor authentication, apply to every session.
When it applies
Requiring SSO takes effect once the connection is on and the domain is verified. A password or social sign-in attempt for the domain then returns Your organization requires single sign-on. Please sign in with SSO. Invited people of the domain accept their invitation by signing in through SSO.
The account owner
The account owner keeps password sign-in while SSO is required, so the account stays reachable when the identity provider is unavailable or misconfigured. Keeping the owner's password current keeps that path ready.
Sessions already open
Sessions that started before SSO was required continue until they expire, within 8 hours. From then on, every sign-in for the domain goes through the identity provider.
Rolling it out
A safe order for turning on SSO for a whole company:
- Set up the connection with Require SSO off, and verify the domain.
- Sign in through SSO with a test person, and check their organization and role.
- Tell people that sign-in moves to the identity provider.
- Turn on Require SSO for everyone.