Skip to content
Last updated:

About SSO and SCIM

Let your users sign in with their corporate account, and let your identity provider create and remove them.

Integration Mapper works with any identity provider that supports SAML 2.0, such as Microsoft Entra ID, Okta, OneLogin, Google Workspace and JumpCloud.

Users type their work email on the sign-in page and are sent to your identity provider, then back to Integration Mapper. Users who sign in for the first time can be created on the spot, with the environment’s default role.

Your identity provider can also create, update and disable users in Integration Mapper, through SCIM 2.0. This is optional and set up per environment. See the SCIM reference.

  • New users get the environment’s default role, normally User.
  • To make someone Admin, tell us who.

Users who sign in with SSO have their password and multi-factor authentication managed by your identity provider. Integration Mapper does not let them set a local password.

  • When you remove a user from the application in your identity provider, or disable them, they can no longer sign in: your identity provider stops letting them through.
  • With SCIM, the same change also reaches Integration Mapper: the user is disabled, and all of their open sessions end at once.
  • Without SCIM, sessions that are already open are not ended by your identity provider. To end them at once, ask us to disable the user. That ends all of the user’s sessions and blocks new sign-ins, even if your identity provider still authorises them.
  • Sign-in starts from Integration Mapper (SP-initiated). Starting from your identity provider’s portal (IdP-initiated) is not supported.
  • Signing out ends the Integration Mapper session and sends the user to your identity provider’s logout page. Full SAML single logout is not supported.
  • One identity provider per environment.