For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Connect
BlogHelp CenterAPI PricingSign up
OverviewElevenCreativeElevenAgentsElevenAPIReception AIAPI referenceChangelog
OverviewElevenCreativeElevenAgentsElevenAPIReception AIAPI referenceChangelog
    • Introduction
    • Models
  • Capabilities
    • Text to Speech
    • Speech to Text
    • Music
    • Text to Dialogue
    • Image & Video
    • Voice Changer
    • Voice Isolator
    • Dubbing
    • Sound Effects
    • Voices
    • Voice Remixing
    • Forced Alignment
    • Voice Agents
    • Speech Engine
  • Administration
    • Account
    • Billing
    • Pay As You Go
    • Consolidated billing
    • Data Residency
    • Usage analytics
    • Files
      • Overview
      • Members
      • Billing groups
      • Service accounts
      • SSO
        • Okta SAML SSO
        • SCIM
      • Sharing resources
      • User groups
      • Model approvals
LogoLogo
Login
Login
Connect
BlogHelp CenterAPI PricingSign up
On this page
  • Overview
  • Guide
  • SCIM
  • FAQ
AdministrationWorkspaces

Single Sign-On (SSO)

An overview on how to set up SSO for your Workspace.
Was this page helpful?
Previous

Okta SAML SSO

Configure Okta as a SAML identity provider for ElevenLabs SSO.
Next
Built with
SSO

Overview

SSO is currently only available for Enterprise customers, and only Workspace admins can enable this feature. To upgrade, get in touch with our sales team.

Single Sign-On (SSO) allows your team to log in to ElevenLabs by using your existing identity provider. This allows your team to use the same credentials they use for other services to log in to ElevenLabs.

Guide

1

Access your SSO settings

Click on your profile icon located in the top right corner of the dashboard, select Workspace settings, and then navigate to the Security & SSO tab.

2

Choose identity providers

You can choose from a variety of pre-configured identity providers, including Google, Apple, GitHub, etc. Custom organization SSO providers will only appear in this list after they have been configured, as shown in the “SSO Provider” section.

3

Verify your email domain

Next, you need to verify your email domain for authentication. This lets ElevenLabs know that you own the domain you are configuring for SSO. This is a security measure to prevent unauthorized access to your Workspace.

Click the Verify domain button and enter the domain name you want to verify. After completing this step, click on the domain pending verification. You will be prompted to add a DNS TXT record to your domain’s DNS settings. Once the DNS record has been added, click on the Verify button.

4

Configure SSO

If you want to configure your own SSO provider, select the SSO provider dropdown to select between OIDC (OpenID Connect) and SAML (Security Assertion Markup Language).

Important: We do not recommend using Microsoft Entra (formerly Azure AD) with OIDC for SSO. For best compatibility and support, use SAML when integrating with Entra/Azure.

Only Service Provider (SP) initiated SSO is supported for SAML. To ease the sign in process, you can create a bookmark app in your SSO provider linking to https://elevenlabs.io/app/sign-in?use_sso=true. You can include the user’s email as an additional query parameter to pre-fill the field. For example https://elevenlabs.io/app/sign-in?use_sso=true&email=test@test.com

Once you’ve filled out the required fields, click the Update SSO button to save your changes.

Configuring a new SSO provider will log out all Workspace members currently logged in with SSO.

SCIM

SCIM is available for Enterprise workspaces, configurable by Workspace admins.
SCIM

SCIM (System for Cross-domain Identity Management) allows your Identity Provider (IdP) to automatically manage users and groups in your ElevenLabs workspace.

FAQ

Microsoft Entra Identifier / Azure AD - SAML

Note: Microsoft Entra (Azure AD) is only supported via SAML. OIDC with Entra is not recommended and may result in login issues.

What to fill in on the Entra / Azure side:

  • Identifier (Entity ID): Use the Service Provider Entity ID value from the ElevenLabs SSO configuration page.
  • Reply URL (Assertion Consumer Service URL): Use https://elevenlabs.io/__/auth/handler
    • For EU residency, use https://eu.residency.elevenlabs.io/__/auth/handler
    • For India residency, use https://in.residency.elevenlabs.io/__/auth/handler
  • ACS URL: Same as the Reply URL above.

What to fill in on the ElevenLabs side:

  • IdP Entity ID: Use the Microsoft Entra Identifier (the full URL, e.g., https://sts.windows.net/{tenant-id}/)
  • IdP Sign-In URL: Use the Login URL from Entra / Azure
Okta - SAML

For Okta-specific setup steps, field mappings, and troubleshooting notes, see Okta SAML SSO.

OneLogin - SAML

What to fill in on the OneLogin side:

  • Recipient: Use https://elevenlabs.io/__/auth/handler
    • For EU residency, use https://eu.residency.elevenlabs.io/__/auth/handler
    • For India residency, use https://in.residency.elevenlabs.io/__/auth/handler
OIDC - Common Errors

Please ensure that email and email_verified are included in the custom attributes returned in the OIDC response. Without these, the following errors may be hit:

  • No email address was received: Fixed by adding email to the response.
  • Account exists with different credentials: Fixed by adding email_verified to the response
I am getting the error 'Unable to login with saml.workspace...'
  • One known error: Inside the <saml:Subject> field of the SAML response, make sure <saml:NameID> is set to the email address of the user.