> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude managed sign-in

> Connect a whole Claude Team or Enterprise organization to a Migma workspace, with no sign-in step for each person.

An administrator turns Migma on once. Every member of your workspace can then use Migma from Claude without signing in or approving access themselves. Claude proves who each person is, and Migma gives them access to that workspace only.

You need a Claude Team or Enterprise organization, and you must be an owner or admin of your Migma workspace.

## Set it up

**1. Add Migma in Claude**

As a Claude Owner or Primary Owner, add Migma as a connector for your organization with the URL `https://migma.ai/mcp`. Open the connector, then in **Authentication** click **Set up** on the **Managed authorization** row.

**2. Copy the Issuer URL**

Under **Identity source**, choose **Claude-issued** and copy the **Issuer URL**. It looks like `https://identity.anthropic.com/issuers/...`.

**3. Trust it in Migma**

In Migma, select the workspace, then open **Settings → API Keys → AI assistants → Claude managed sign-in**. Turn it on, paste the Issuer URL, and save.

**4. Name your workspace in Claude**

Copy the **Tenant ID** from the same place in Migma, and paste it into **Tenant ID** in Claude's setup. This keeps sign-in working if another workspace ever enters the same Issuer URL.

**5. Run the test**

In Claude, click **Run test** under **Connection status**. Claude shows each step and what came back.

## Who can connect

A person connects when both of these are true:

* They are a member of the Migma workspace, and the email address of their Claude account is the address they use in Migma.
* They have verified that email address in Migma. Your Migma settings show how many members can connect.

Migma does not create accounts through this connection. Invite people to the workspace first.

## What a connection can reach

* Only this workspace, even when the person also belongs to other Migma workspaces or has their own brands.
* Only the brands their role allows, with the same permissions they have in the app.
* Designing and editing emails, audiences, campaigns and their approvals, exports, and reading sending domains.

Everything else stays in Migma: single sends, buying or changing domains, webhooks, plan changes, sending metrics, device previews, connected tools, and creating brands. Contact imports must be sent as text, not as a file upload. You approve every send in Migma.

## Turn it off

Turn off **Claude managed sign-in** in Migma, or change the Issuer URL. Tokens from the old setting stop working right away, and removing someone from the workspace stops their access right away too. Access tokens otherwise last one hour, and Claude renews them while the person remains a member of your Claude organization.

## If the connection test fails

| Message | What to do |
| - | - |
| No workspace trusts this issuer | Save the Issuer URL in Migma, with Claude managed sign-in turned on. |
| More than one workspace trusts this issuer | Enter your workspace's Tenant ID in Claude's setup. |
| This person is not a member of the workspace | Invite them in Migma, using the email address of their Claude account. |
| This person has not verified their email address in Migma | They can verify it in **Settings → Security**. |

Identity provider assertions, such as Okta Cross App Access, are not supported yet. Choose **Claude-issued**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.