Sign in with your identity provider
Connect Okta, Microsoft Entra ID, Google Workspace, or another OIDC or SAML provider. Verify a domain and require SSO for it.
A workspace with staff accounts should not depend on a separate password for each tool.
Enterprise SSO is now available on Pro.
Connect
Use OpenID Connect or SAML 2.0 with Okta, Microsoft Entra ID, Google Workspace, or another provider.
Enforce
Prove control of a work-email domain with a DNS TXT record, then require SSO for it. Email and Google sign-in are refused for those members.
Provision
A first-time SSO signer can join automatically when their asserted directory group maps to a workspace role.
MFA, sign-in policy, and offboarding stay with the identity provider, where they already live. The workspace gets access control without becoming another password store. SCIM provisioning is separate and works with or without SSO.
Related