Enable Single Sign-On (SSO) for your Makeshapes organization to provide your team members and/or participants with a secure and convenient way to access Makeshapes experiences using their existing company credentials.

Single Sign-On allows users to log in once with one set of credentials (managed by your organization's Identity Provider - IdP) to access multiple applications, including Makeshapes.

Note: The availability of Creator and/or Participant SSO may be subject to your Makeshapes service plan and/or configuration.

Makeshapes offers two types of SSO integration:

Your internal team (Administrators, Creators, Editors) accessing the Makeshapes platform to create and manage experiences. This provides secure, managed access for your staff using their company credentials.

When SSO is enabled, we recommend disabling Multi-Factor Authentication (MFA) with Makeshapes to further leverage your Identity Provider's MFA policies for users authenticating via SSO. However, for enhanced security, MFA is always recommended for team members without SSO.

If learners have company accounts and you require them to authenticate before accessing content, this option would be recommended.

In addition, if you need Makeshapes to capture specific learner attributes (like an Employee ID) from your IdP. This is often essential for integrations, such as identifying learners by Employee ID in xAPI statements sent to your LRS .

Participant SSO requires learners to authenticate, which might be an extra step if they are not already logged into their company network. This may introduce access roadblocks for external participants or those who have trouble with their company login or their personal device.

For maximum ease of access, Makeshapes allows learners to join experiences by simply providing their name and email, without requiring them to authenticate via your company's SSO. This is often preferred for broad participation and reduces potential login friction.

Makeshapes supports SSO integration with a variety of Identity Providers (IdPs). Here are our currently supported options:

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).