SSO Setup

Single sign-on (SSO) lets your team sign in to Anima with your company's identity provider (IdP), such as Okta, Microsoft Entra ID, or Google Workspace. Anima supports SSO through SAML 2.0.

Anima's support team sets up SSO together with you. This page covers what you need to do on your side.

Before you start

Make sure you have the following.

• An appropriate plan. SSO requires a plan that includes it. If you are not sure whether your team's plan does, contact [email protected].
• An identity provider that supports SAML 2.0.
• Admin access to your IdP, so you can create a new SAML application and export its metadata.
• Your company email domain(s), for example yourcompany.com.
• A team owner. This is the person who will own SSO for your domain and manage your team on Anima.

How setup works

1. Contact Anima support

Email [email protected] with the subject "SSO setup request" and include:

• Your company name
• The email domain(s) you want to enable
• The name and email address of your team owner
• The name of your identity provider
• Your IdP metadata XML file, attached to the email
• Any signing requirements your IdP has for SAML messages

2. Receive Anima's SP metadata

Anima support configures SSO for your domain and sends you our service provider (SP) metadata XML file. It contains everything your IdP needs, including:

• The Assertion Consumer Service (ACS) URL, also called the Response URL
• The Login URL
• The attributes Anima expects in the SAML response

3. Configure Anima in your IdP

In your identity provider:

1. Create a new SAML application for Anima, using the SP metadata file from support.
2. Map the user's email address and display name to the attributes listed in the metadata. Enter each attribute name exactly as listed, in full.
3. Assign the application to the users or groups who should have access to Anima.

4. Test the sign-in

Let support know when the application is configured. Then sign in to Anima with SSO using a work email address from your domain. Support can stay with you until the first sign-in succeeds.

Good to know

• Authentication method and MFA. Anima does not require a specific authentication method. Your IdP's own policies, such as multi-factor authentication, apply when your team signs in.
• Sharing files safely. Send only the metadata XML file. Never send private keys, passwords, or client secrets.
• Changes to your IdP. If your IdP metadata changes, for example when a certificate is renewed or you switch providers, send the updated metadata file to [email protected].

Troubleshooting

"Organization not found" when signing in with SSO
SSO is not yet enabled for the email domain you used, or the domain differs from the one registered with Anima. Contact [email protected] with the email address you tried.

Sign-in fails at your identity provider
Check that the user is assigned to the Anima application in your IdP.

Any other sign-in error
Send support the exact error message, the email address used, and the time it happened.

Contact

For SSO setup, plan questions, and troubleshooting, contact [email protected].