> ## 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. # Auto-connect Tella in Claude for your organization > Claude Team and Enterprise admins can connect Tella for every member at once with Claude-issued auth (beta), so members use Tella in Claude without signing in or approving access. It needs a verified domain on your Tella workspace. Claude Team and Enterprise admins can connect Tella for their whole organization at once, so members use Tella in Claude with no sign-in page or consent screen. Claude calls this **Enterprise-managed auth**. Tella supports its **Claude-issued** identity source, which is in beta and needs no identity provider or SSO. > [!NOTE] > > Auto-connect is in beta. While it is, Tella support registers your organization's issuer URL for you (step 2 below). A setting in Tella will replace that step later. ## What you need before you start * **A Claude Team or Enterprise plan**, and someone who can open **Organization settings** in Claude. * **A Tella workspace with a verified domain.** A workspace owner verifies it in Tella under **Settings → Security → Verify your domain**. Once a domain is verified, anyone who signs in to Tella with an email on it joins your workspace automatically and takes a billable seat. * **Matching email addresses.** Claude matches each member by email. A member is connected only if their Claude email is the same as the email on their Tella account, that email is on your verified domain, and they're already a member of your Tella workspace. ## Does auto-connect add Tella members or seats? No. Auto-connect only signs in people who are already members of your Tella workspace. It never creates a Tella account or adds anyone to your workspace, so it can't change your seat count. Members without a matching Tella account see Claude's usual **Connect** prompt instead. ## Set up auto-connect 1. **Copy your issuer URL in Claude.** Go to **Organization settings → Connectors** and select **Tella**. On the **Configuration** tab, click **Set up** next to **Managed authorization**, choose **Claude-issued** under **Identity source**, and copy the issuer URL. It looks like `https://identity.anthropic.com/issuers/...`. 2. **Send it to Tella support.** Email [support@tella.com](mailto:support@tella.com) with the issuer URL and your Tella workspace name. We'll reply once it's registered on your workspace. 3. **Leave the tenant field empty** unless Tella support gives you a tenant ID. 4. **Test the connection.** Back in Claude, click **Test connection**, then **Enable and continue**. 5. **Choose who gets Tella.** All roles get it by default. To try it with one team first, pick only that team's custom role. Before you announce it, ask two or three members to open a new chat and run a real request, such as "List my latest Tella videos". ## If the connection test fails Check these, in order: * The issuer URL you sent matches the one Claude shows now. Switching **Identity source** in Claude can change it. * Your Tella workspace has a verified domain. * The person running the test is a member of the Tella workspace, signed in with the same email as their Claude account, on the verified domain. If it still fails, email [support@tella.com](mailto:support@tella.com) with the error Claude shows. ## What members see in Claude Tella is already connected the first time a member needs it, with no sign-in page or consent screen. Tella acts as that member and can do what they can do in Tella, including editing and sharing their videos. A member whose email doesn't match a Tella account sees the usual **Connect** prompt and can sign in to Tella themselves. ## When someone leaves your organization Remove them from your Claude organization and from your Tella workspace (**Settings → Members**). Removing them from Claude stops new sign-ins, but access Claude already has lasts until it expires. Remove them from Tella before their email address is given to someone else, or the new person could be signed in to the old account. ## What Claude checks before connecting a member Claude only checks that the person is a current member of your Claude organization. It doesn't check SSO or two-factor authentication. Claude recommends enforcing SSO on your Claude organization if you need that. ## Turn auto-connect off In Claude, open Tella's **Managed authorization** settings and choose **Disable**. Members then connect Tella themselves. To also remove the issuer from your Tella workspace, email [support@tella.com](mailto:support@tella.com). ## Can I auto-connect through Okta instead? Not yet. Claude also offers an **IdP-managed** identity source, where Okta signs members in, but Tella doesn't support it yet. Claude-issued works whatever identity provider you use, including Google Workspace and Microsoft Entra ID. ## Related articles * [Tella MCP Server](https://www.tella.com/docs/help/integrations/mcp-server.md): connect Tella to Claude yourself, and the other AI tools Tella works with. * [Set up SSO](https://www.tella.com/docs/help/admin/set-up-sso.md): sign in to Tella with your identity provider. * Claude's guide: [Auto-connect your organization's apps to Claude](https://support.claude.com/en/articles/15537633-auto-connect-your-organization-s-apps-to-claude). ## Related topics - [Record with AI agents using Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture.md) - [Make videos for your help articles with Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture-help-center-videos.md) - [Use your ChatGPT or Claude plan with the Tella Agent](https://www.tella.com/docs/help/integrations/use-your-chatgpt-or-claude-plan.md) - [Get started with Auto Capture](https://www.tella.com/docs/help/integrations/auto-capture-get-started.md) - [Connect Tella with Zapier](https://www.tella.com/docs/help/integrations/connect-tella-with-zapier.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.