Skip to main content
Single sign-on (SSO) lets your team log in to Tella with Okta, Microsoft Entra ID, Google Workspace, or any SAML 2.0 / OIDC provider. Workspace owners set it up under Settings → Security → Single sign-on (SSO); it’s a paid add-on on Pro and Premium and included on Enterprise.
On Pro and Premium plans, SSO costs $125 per month (or $1,500/year on annual plans) on top of your subscription. On Enterprise plans it’s included at no extra charge. To buy multiple Enterprise licenses, email sales@tella.com.

How does SSO work in Tella?

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.

Is SSO enforced by default?

Yes. As soon as your SSO connection is live, it’s enforced for every domain you’ve verified: anyone whose email is on one of those domains has to sign in through your identity provider, and email codes or Google sign-in no longer work for them. People whose email is on a domain you haven’t verified, such as contractors or guests, keep signing in the way they do today.

Which identity providers are supported?

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

Set up SSO

Setup is self-serve and takes a few minutes. You 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, but you’re not charged until your connection goes live. On Enterprise plans 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. Once the connection is live, everyone on a verified domain must use SSO.
  4. Connect your identity provider: open the guided setup to connect Okta, Microsoft Entra ID, Google Workspace, or any SAML/OIDC provider. It 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, check that team members can log in through your identity provider.

What happens after SSO is enabled

  • Members visit tella.com and log in using your identity provider.
  • Members with an email on your verified domains can only sign in through your identity provider.
  • New members who authenticate through your identity provider are automatically added to your workspace.

Turn SSO off

Workspace owners can disable SSO (or cancel an in-progress setup) under Settings → Security → Single sign-on (SSO), in the Danger zone. 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 or Google login alongside SSO?

Not if their email is on a domain you’ve verified: SSO is enforced for verified domains, so those members must sign in through your identity provider. Members with an email on any other domain can still use email or Google sign-in.

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 automatically removes members when they leave your directory and keeps profile details in sync.

Where can I find Tella’s security documentation?

Tella is SOC 2 Type II compliant. Visit our Trust Center for details on security practices, compliance, and data protection, and to request the SOC 2 report.
Last modified on November 19, 2026