Built LMS Help Center
Settings

Configure SAML SSO

Set up SAML 2.0 sign-in for Built LMS with a supported identity provider.

Use SAML SSO when your organization signs users in through an identity provider such as JumpCloud, Okta, Microsoft Entra ID, Ping, OneLogin, Auth0, or another SAML-compatible IdP.

In this setup:

  • Built LMS is the Service Provider or SP.
  • Your identity provider is the Identity Provider or IdP.
  • Built LMS receives SAML assertions at the ACS URL shown on the SAML provider page.
  • Built LMS requires a stable user email address for profile matching.

Before you begin

You need:

  • Built LMS admin access to Settings > Identity & Access > Authentication.
  • Permission to add or edit authentication providers.
  • Admin access in the identity provider.
  • A SAML app in the IdP, or permission to create one.
  • A pilot user assigned to the IdP app.
  • A non-SSO admin recovery path while you test.

Do not make SAML the default sign-in method until a pilot user can sign in and a non-SSO admin recovery path still works.

Choose the SAML task you need

Use the focused guide that matches what you are doing now:

How SAML works in Built LMS

SAML sign-in depends on an exact match between the Built LMS provider values and the IdP app:

Built LMS valueIdP field name may be called
SP Entity IDAudience URI, SP Entity ID, Entity ID, Identifier
ACS (Assertion Consumer Service) URLACS URL, Reply URL, Recipient URL
NameID FormatNameID format
X.509 CertificateSigning certificate, verification certificate

Copy these values from the Built LMS SAML provider page for the current environment. A staging domain, production subdomain, and custom domain are different SAML applications from the IdP's point of view.

Verify success

SAML is ready for rollout when:

  • The provider is saved and enabled.
  • A pilot user can sign in from the Built LMS login page.
  • The user returns to the expected learner, manager, or admin portal.
  • The email value from the IdP matches the intended Built LMS user identity.
  • A non-SSO admin recovery path still works.

Troubleshooting

On this page