SAML 2.0 Single Sign-On is available on all Atatus plans, including Free and Trial accounts. Any account Owner or Admin can configure SSO under Settings » Account Settings » Single Sign-on. The only accounts excluded from configuring custom SAML SSO are those provisioned directly through the Heroku Add-on marketplace.
No. Enabling SSO does not revoke or disable passwords for existing users. Users who created an account or were invited before SSO was configured can continue logging in with their email and password. This design prevents administrative lockouts during IdP maintenance. However, users provisioned automatically via SAML JIT have password logins and password resets permanently blocked.
Yes. You do not need to pre-invite users manually. When an assigned user authenticates through your IdP for the first time, Atatus automatically creates their account with the User role. If an existing Atatus user from another organization signs in via your IdP, they are automatically joined to your account.
No. Atatus does not parse group or role claims from the SAML assertion. All users provisioned via JIT start with the User role. Account Owners and Admins can promote users to higher privileges in the Atatus dashboard under Settings » Users.
When a user signs in via SAML SSO, Atatus completely suppresses native in-app two-factor authentication. All multi-factor authentication (MFA) and conditional access controls must be enforced directly within your Identity Provider.
Atatus SSO sessions remain valid for 30 days. The session expiration timer refreshes automatically each time the user signs in.
No. Single Logout is not supported. When a user clicks Log Out in Atatus, their local Atatus session is terminated, but their IdP session remains active.
The SSO Account ID Alias is a customizable identifier (minimum 4 characters) that you can configure under Settings » Account Settings » Single Sign-on. Setting an alias allows your team to navigate to a branded direct login URL (such as https://app.atatus.com/login/saml/acme-corp) instead of entering your 24-character Account ID.
No. Atatus requires that your Identity Provider metadata contains exactly one active signing certificate. If your metadata descriptor contains multiple signing certificates (such as during an uncommitted certificate rollover), Atatus certificate validation will fail. Ensure only the active certificate is published in the metadata uploaded to Atatus.
No. Each Atatus account can be linked to only one SAML Identity Provider at a time.
In the Atatus dashboard, navigate to Settings » Account Settings » Single Sign-on. To temporarily pause SSO authentication, turn the Enabled toggle switch to OFF. To permanently delete your IdP metadata and configuration, click the red Remove Single Sign-on button.