Single Sign-On, or SSO, lets people sign in to Knowly through your organisation's normal identity provider. It is usually set up together with Knowly.
Availability
SSO is usually available for organisations with an Enterprise setup.
If SSO is not available in your organisation, contact Knowly before planning the rollout around it.
What SSO changes
With SSO, people use their organisation account instead of a separate Knowly password. Knowly may send them to your organisation's sign-in screen when they open Knowly.
For admins, SSO can also affect whether account details like email or password are edited in Knowly or in the identity provider.
Knowly has two SSO modes. In one, everyone signs in through your identity provider; in the other, only administrators and team members do, while other participants and managers keep using their email link. Which one fits depends on whether you need to invite people from outside your identity provider. See SSO modes in Knowly for the full comparison.
SAML and identity providers
Many organisations use SAML for SSO. SAML is the protocol behind the sign-in connection, not a separate Knowly feature you need to manage day to day.
Your IT or identity team usually provides the technical details Knowly needs. Knowly then helps confirm the setup and sign-in flow.
Before you turn on SSO
Check these things before rollout:
which email domains should sign in through SSO
who should be able to administer Knowly
whether existing admins can still access Knowly during the change
how participants and managers will receive their learning journey links
If your organisation also uses directory provisioning, removals and access changes may need to happen in the identity provider rather than directly in Knowly.
A common snag right after turning on SSO: a new administrator is added in Knowly but still can't sign in, usually because they haven't been added to the identity-provider group connected to Knowly yet. See I've been added as an administrator but can't sign in if that happens.