TL;DR
Set up single sign-on (SSO) so your team signs in to Atlan with their existing identity provider credentials. Configure SAML 2.0 with Okta, Azure AD, Google, JumpCloud, OneLogin, PingFederate, or any custom SAML provider.
Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect
Set up single sign-on (SSO)
Single sign-on (SSO) lets your team sign in to Atlan with the credentials they already use in your identity provider, instead of a separate Atlan email and password. Atlan uses SAML 2.0, so any SAML-compatible provider works. Set up SSO when your team is growing, when sign-in should route through your identity provider, or when IT manages access centrally.
Pick your identity provider below. Okta and Azure AD also support SCIM provisioning to automate the user lifecycle; the other providers support SSO only.