Enable Azure AD for SCIM provisioning
Automate user and group lifecycle in Atlan by connecting Microsoft Entra ID over SCIM 2.0: generate a SCIM token in Atlan, configure automatic provisioning in Entra, verify attribute mappings, and start syncing.
Automate user and group lifecycle in Atlan by connecting Microsoft Entra ID over SCIM 2.0: generate a SCIM token in Atlan, configure automatic provisioning in Entra, verify attribute mappings, and start syncing.
Configure SAML 2.0 single sign-on between Microsoft Entra ID (Azure AD) and Atlan so your users sign in to Atlan with their existing Microsoft credentials. Exchange service provider and identity provider metadata, assign users in Entra, and optionally sync Azure AD groups to Atlan.
Configure SAML 2.0 single sign-on between Google Workspace and Atlan so your users sign in to Atlan with their Google credentials. Exchange service provider and identity provider metadata, assign users in Google Admin Center, and optionally sync Google groups to Atlan.
Configure SAML 2.0 single sign-on between JumpCloud and Atlan so your users sign in to Atlan with their JumpCloud credentials. Exchange service provider and identity provider metadata, assign user groups in JumpCloud, and optionally sync JumpCloud groups to Atlan.
Automate Okta user and group lifecycle in Atlan with SCIM 2.0. Provision new users, keep attributes in sync, deactivate leavers, and optionally push groups from Okta to Atlan.
Configure SAML 2.0 single sign-on between Okta and Atlan so your users sign in to Atlan with their Okta credentials. Exchange service provider and identity provider metadata, assign users in Okta, and optionally sync Okta groups to Atlan.
Configure SAML 2.0 single sign-on between OneLogin and Atlan so your users sign in to Atlan with their OneLogin credentials. Exchange service provider and identity provider metadata, assign users in OneLogin, and optionally sync OneLogin groups to Atlan.
Configure SAML 2.0 single sign-on between any SAML-compatible identity provider and Atlan so your users sign in with their existing IdP credentials. Exchange service provider and identity provider metadata, then optionally sync IdP groups to Atlan.
How to get people into your Atlan workspace and give them the right baseline access. A small team can be managed by hand; a larger organization connects an identity provider for SSO and SCIM. Covers authentication, users, groups, and roles.
Integrate Atlan with identity management tools like SCIM and SSO.
Prevent Atlan from auto-provisioning an account for every user who can authenticate against your identity provider. Restrict access to only the users and groups your IdP explicitly assigns to the Atlan application.
Integrate Atlan with SCIM to automate user provisioning.
SCIM 2.0 automates user and group lifecycle in Atlan from your identity provider: provision new users, keep attributes in sync, and auto-deprovision leavers. Supported with Azure AD / Entra and Okta.
Set the role Atlan assigns to new users on their first SSO sign-in. Use Member for most workspaces, Guest for read-only users, or Admin for elevated access.
Answers to common questions about Atlan SSO integration, Azure AD setup, user provisioning, invite emails, and data processing.
Configure SAML 2.0 single sign-on between PingFederate and Atlan so your users sign in to Atlan with their PingFederate credentials. Copy Atlan's service provider metadata into PingFederate, configure both ACS endpoints, and import PingFederate's IdP metadata back into Atlan.
Troubleshoot common SCIM provisioning issues in Atlan, including missing group members, username conflicts, token expiry, and identity provider sync behavior.
Fix common SSO sign-in problems in Atlan, including first-time login errors, username mismatches, provider-specific issues, and group sync behavior.