Skip to main content
All CollectionsAPIs and Integrations
How do I configure SSO for Synthesia?
How do I configure SSO for Synthesia?

Learn more about how to configure SSO

Updated this week

To configuring SSO for Synthesia:

Step 1: Configure Your Identity Provider (IdP)

  1. Create a SAML 2.0 Application:

    • Follow your IdP's instructions to create a SAML 2.0 single sign-on application.

    • Refer to vendor-specific guides if needed:

  2. Set Required Synthesia-Specific Details:

    1. Single Sign-On URL (Assertion Consumer Service URL):

    2. Audience URI (Entity ID):

      • urn:amazon:cognito:sp:eu-west-1_7hEawdalF

    3. Name Identifier:

      • Set the NameID field to the user's email address in lowercase. Ensure it matches the email claim.

  3. Add Required Claims:

    • Include the following claims in your IdP configuration:

      • company

      • email

        • It has to be in lower case. Use the function ToLowercase, often user altogether ToLowercase( user.mail )

        • It has to have NO namespace

        • It has to be named email . Other variations such as emailaddress or email_address are not valid.

      • family_name

      • given_name

      • picture (optional)

  4. Ensure there is no namespace in the claims (For Azure AD: set the namespace to blank).

Step 2: Share Metadata with Synthesia

  1. Obtain Metadata URL. Your IdP will provide a Metadata URL after configuration.

  2. Send the following details to Synthesia support:

    1. Metadata URL

    2. Identifiers (domains to associate with SAML SSO, e.g., 'example.com')

Step 3: Testing Phase

  1. Synthesia support will process the metadata file and enable a testing phase. During this phase:

    1. Users can still log in with email and password.

    2. SSO login is available for testing.

  2. Test SSO Login by logging out of Synthesia.

  3. Use the unique SSO URL provided by Synthesia support.

  4. Log in via your IdP using your professional email address.

Step 4: Enforce SSO

  1. Confirm that the SSO login works for all test users.

  2. Contact Synthesia support to enforce SSO for your organization. Please provide:

    • Validation that tests were successful.

    • A list of domain names managed by your IdP (e.g., 'synthesia.io').

  3. Once enforced, login via email and password will be disabled for all users within your organization.

For additional information see the Synthesia SSO documentation page.

Notes:

Related Articles
What is the Synthesia password policy?
How do I create a Synthesia Brand Kit?
Why is my SSO not working?
How can I prevent self-serve subscriptions for SSO users in my organization?
How do I setup Azure AD for SSO Configuration with Synthesia?
Did this answer your question?