Skip to content
Last updated:

Set up SSO

The values to exchange with the Integration Mapper team, and the steps on your identity provider.

SSO is set up per environment, together with the Integration Mapper team.

  1. We send you the values for your environment: the Entity ID, the reply URL (ACS), the logout URL and the metadata URL.
  2. You create an enterprise application in your identity provider with those values, and assign the users or groups who should have access.
  3. You send us your identity provider’s federation metadata URL or XML.
  4. We enable SSO for your corporate email domains.

The values follow this pattern, where {host} is your environment’s address and {tenant} its identifier:

ValuePattern
Entity IDhttps://{host}/saml/{tenant}
Reply URL (ACS)https://{host}/api/auth/saml/{tenant}/callback
Logout URLhttps://{host}/api/auth/saml/{tenant}/logout
Metadatahttps://{host}/api/auth/saml/{tenant}/metadata

Use the exact values we send. Do not build them by hand.

The email claim must be present in the SAML response. In Microsoft Entra ID, check Attributes & Claims for emailaddress. The response must have a signed assertion; this is the default in Microsoft Entra ID.

On the sign-in page, type a work email from an enabled domain. The password field is replaced by Sign in with SSO, which takes you to your identity provider and back.

  1. We send you the SCIM endpoint, https://{host}/scim/v2/{tenant}, and a token. The token is shown only once; keep it in your identity provider.
  2. You turn on automatic provisioning in the same enterprise application. In Microsoft Entra ID: Provisioning, mode Automatic, with the endpoint as Tenant URL and the token as Secret Token.
  3. You test the connection, and start provisioning for the users and groups assigned to the application.

What each attribute becomes, and what disabling a user does, is in the SCIM reference.