Single Sign-On (SSO) enables your team members to authenticate through your organization’s centralized identity provider (IdP) instead of managing separate credentials in Atatus. Atatus supports identity federation using the industry-standard Security Assertion Markup Language 2.0 (SAML 2.0) protocol.

Core SAML Concepts

If you are setting up SAML SSO for the first time, review these key terms:

How SSO Works in Atatus

Atatus supports both Service Provider-Initiated (SP-Initiated) and Identity Provider-Initiated (IdP-Initiated) login flows.

Supported Identity Providers

Atatus integrates with any identity provider compliant with the SAML 2.0 specification. Pre-configured guides are available for:

Prerequisites and Permissions

Before enabling SSO in Atatus, ensure you satisfy the following:
  • Atatus Permissions: You must hold the Owner or Admin role in Atatus (account.sso.manage permission). Accounts provisioned via the Heroku Add-on cannot configure custom SAML SSO.
  • Subscription Plan: SAML SSO is available across all Atatus subscription plans, including free and trial tiers.
  • IdP Administrator Access: You must possess administrator privileges in your Identity Provider (such as Okta Super Admin, Microsoft Entra Application Administrator, or Google Workspace Super Admin) to create applications and assign users.

Required SAML Attributes

Your Identity Provider must return a signed SAML assertion containing the user’s primary email address and optional name attributes:
Atatus resolves attributes strictly by their exact Name key. Atatus does not inspect FriendlyName attributes or WS-Federation claims (such as http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress or givenName/surname). Ensure claims are configured using the exact attribute names listed above.