Skip to main content

Single sign-on (SSO)

Let your team or your learners log in to Makeshapes with their company account, and choose which kind of SSO fits.

Written by Cody Iddings

With single sign-on (SSO), your team, your learners or both can log in to Makeshapes with their existing company account.

What is SSO?

SSO lets people log in once, with one set of credentials, to use several applications, including Makeshapes. Your organization's identity provider (IdP) manages those credentials.

Benefits of using SSO with Makeshapes

  • Fewer passwords: people don't need a separate Makeshapes password.

  • Stronger security: logging in goes through your IdP, so your existing security policies apply, such as multi-factor authentication (MFA).

  • Central user management: you can often manage access from your IdP, which makes onboarding and offboarding simpler.

  • One login: people use the same company login they use for other tools.

SSO for your team and SSO for learners are part of the Enterprise plan. Makeshapes sets them up for your organization. To see which ones you have, open Organisation settings and click Plan. They show as Single sign-on for your team and Single sign-on for learners.

The Plan page in Organisation settings, with the Single sign-on for your team and Single sign-on for learners rows

SSO options with Makeshapes

Makeshapes offers two types of SSO:

Team member SSO (recommended)

Team member SSO is for your internal team, such as administrators, creators and editors, who log in to Makeshapes to create and manage experiences. Your staff get secure, managed access with their company credentials.

When SSO is on, we recommend turning off Makeshapes MFA for people who log in with SSO, and relying on your IdP's MFA policies instead. For team members who don't use SSO, we always recommend MFA.

Learner SSO

We recommend learner SSO if your learners have company accounts and must log in before they can use your content.

It can also be useful if you need Makeshapes to capture learner details, such as an employee ID, from your IdP. The xAPI integration, though, identifies learners by their email address. For more information, see xAPI and your learning record store.

Learner SSO adds a login step, which can get in the way if learners aren't already logged in to their company network. It can also block external learners, or people who have trouble with their company login or are on a personal device.

Without learner SSO, learners join an experience with only their name and email address. This is often better for broad participation, because there's no login to get past.

Log out and log back in

When someone clicks Log out in Creator, they land on a page that says You're logged out. If their session runs out, the page says Your session ended instead.

The You're logged out page, with the Makeshapes logo and a Log in button

To get back in, click Log in. On your organization's own Creator address, this takes you to your IdP login, not to the Makeshapes email step.

Supported SSO protocols

Makeshapes supports SSO integration with a range of identity providers. These are the supported options:

  • Custom SAML 2.0

  • Microsoft Entra ID (formerly Azure AD) - SAML

  • Microsoft Entra ID (formerly Azure AD) - WS-Federation or OpenID Connect (OIDC)

  • Google Workspace (SAML)

  • Okta (SAML)

  • Cloudflare (SAML)

While the general setup principles are similar, the exact metadata exchanged and configuration steps may vary slightly depending on the protocol (SAML 2.0, OIDC, WS-Federation).

Did this answer your question?