> ## Documentation Index > Fetch the complete documentation index at: https://www.tella.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Set up SSO Single sign-on (SSO) lets your team log in to Tella using your company's identity provider — like Okta, Microsoft Entra ID, Google Workspace, or any SAML 2.0 / OIDC provider. SSO is a paid add-on for Pro and Premium plans: \$125 per month (or \$1,500/year on annual plans) on top of your subscription. On Enterprise plans SSO is included — no add-on charge. Workspace owners can enable it self-service under **Settings → Security**. Enterprise customers looking to purchase multiple licenses can also reach out to [sales@tella.com](mailto:sales@tella.com). ## How it works Once SSO is enabled for your workspace, members sign in through your identity provider instead of using a separate Tella password. New members who authenticate through your identity provider get a Tella account automatically on their first sign-in. ## Supported identity providers Tella supports SAML 2.0 and OIDC-based SSO with any compatible provider, including: * **Okta** * **Microsoft Entra ID (Azure AD)** * **Google Workspace** * **OneLogin** * **JumpCloud** * **PingFederate** * **Any SAML 2.0 / OIDC-compatible provider** ## Getting started Setting up SSO is self-serve and takes a few minutes. You'll need to be a workspace owner on an active paid subscription (SSO can be enabled once a trial converts to a paid plan). 1. **Open SSO settings** — go to **Settings → Security** and select **Single sign-on (SSO)**. 2. **Set up SSO** — click **Set up SSO** and confirm. On Pro and Premium plans this adds the \$125/month add-on to your subscription — you're not charged until your connection goes live. On Enterprise plans SSO is included, so there's no extra cost. 3. **Verify your domain** — add your company domain and follow the instructions to add the DNS record we give you. This proves you own the domain so sign-ins from it route to your identity provider. 4. **Connect your identity provider** — open the guided setup and follow the steps to connect Okta, Microsoft Entra ID, Google Workspace, or any SAML/OIDC provider. The flow walks you through adding Tella as an application in your provider and entering the required details. 5. **Test the connection** — once your connection is active, verify that your team members can log in through your identity provider. ## What happens after SSO is enabled * Members visit [tella.tv](https://tella.tv) and log in using your identity provider. * New members who authenticate through your identity provider are automatically added to your workspace. * Members can still belong to multiple Tella workspaces. ## Turning SSO off Workspace owners can disable SSO — or cancel an in-progress setup — under **Settings → Security → Single sign-on**. Members go back to email or Google sign-in, the add-on is removed from your subscription, and unused time is credited. If you're still setting up and your connection hasn't gone live, nothing has been billed yet. ## FAQ ### Can members use email/password login alongside SSO? This depends on your workspace configuration. [Contact us](mailto:sales@tella.com) if you want to restrict login to SSO only. ### What happens to existing members when SSO is enabled? Existing members will be prompted to log in through your identity provider on their next session. Their videos and workspace access are preserved. ### Can I use SSO with multiple workspaces? Yes. Each workspace can have its own SSO connection, and members can belong to multiple workspaces. ### Should I set up SCIM too? Most teams enable both. SSO handles sign-in and can add users when they first authenticate, while [SCIM provisioning](/help/admin/scim-provisioning) automatically removes members when they leave your directory and keeps profile details in sync. ### Where can I find Tella's security documentation? Visit our [Trust Center](https://trust.tella.com) for details on security practices, compliance, and data protection.