One read of Claude Documentation

 
 To keep Claude out of channels by name ahead of time, add a [blocked channel pattern](#block-or-auto-join-channels-by-name) instead.
 
-Steps 1–3 do not delete any data. Step 4 (removing the scope) deletes the channel's data. Step 5 (deleting a bundle) removes the credentials in that bundle; memory, routines, and session transcripts are unaffected. Removing Claude from a channel stops it responding there; the channel's memory and routines remain on record, and re-adding it restores them. To delete data without uninstalling, use the dedicated controls at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag).
+Steps 1–3 do not delete any data. Removing Claude from a channel stops it responding there; the channel's memory and routines stay on record, and re-adding Claude restores them.
+
+Steps 4 through 6, and disconnecting the workspace, each delete something different:
+
+* **Remove the channel's scope (step 4):** deletes the channel's sessions, memory, routines, and published artifacts. Claude keeps answering in the channel with the access it inherits from its workspace; see [what each action deletes](/docs/claude-tag/concepts/data-lifecycle#actions-in-claude).
+* **Delete the bundle (step 5):** removes the credentials in that bundle. Memory, routines, and session transcripts stay.
+* **Uninstall the app (step 6):** Anthropic deletes the workspace's Claude data, the same set as disconnecting the workspace, plus the app's installation credential; see [what each action deletes](/docs/claude-tag/concepts/data-lifecycle#actions-in-slack).
+* **[Disconnect the workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing)** at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag): Anthropic deletes the workspace's sessions and transcripts, memory, routines and artifacts, scopes, and members' account links, and the app stays installed so a workspace admin can pair again; see [what each action deletes](/docs/claude-tag/concepts/data-lifecycle#actions-in-claude).
+
+Access bundles belong to your organization, not to a workspace, so uninstalling or disconnecting keeps them; only their bindings to that workspace's scopes go. To delete one channel's data while Claude stays in the workspace, remove that channel's scope (step 4) rather than uninstalling.
 
 ### Limit Claude Tag to specific channels
 

 4. Optionally configure OAuth Client ID/Secret in Advanced settings
 5. Click "Add"
 
+If your Add custom connector dialog has two steps, see [The Add custom connector dialog, field by field](#the-add-custom-connector-dialog-field-by-field).
+
 **Members then:**
 
 1. Go to **Customize > Connectors**

 4. Optionally configure OAuth credentials
 5. Click "Add"
 
+If your Add custom connector dialog has two steps, see [The Add custom connector dialog, field by field](#the-add-custom-connector-dialog-field-by-field).
+
 ### Enabling connectors in chat
 
 Use the "+" button in your chat interface to access "Connectors," where you can enable/disable connectors per conversation.
 
+## The Add custom connector dialog, field by field
+
+<Note>
+  The two-step dialog described here is rolling out gradually. If your dialog shows a name, URL, and Advanced settings on one screen, your organization has the earlier version; the steps above still apply.
+</Note>
+
+**Name**: the display name shown in the connectors list.
+
+**Remote MCP server URL**: the HTTPS address where the server accepts MCP requests, for example `https://mcp.example.com/mcp`. After you continue, Claude checks the URL and pre-fills the authentication settings it detects, marked "Detected."
+
+**Authentication**: how people connect to the server.
+
+* **Always required**: each user signs in through the server's OAuth flow before using it.
+* **Required when the server asks**: Claude connects without credentials and prompts users to sign in when the server asks.
+* **None**: no sign-in. Anyone with access to the server URL can use the connector. If the server uses an API key, choose None and add the key under **Request headers**; Claude stores it as the connector's credential.
+
+**OAuth client** (shown unless you chose None): how Claude identifies itself to the server's authorization server.
+
+* **Use Anthropic's hosted client metadata** (recommended): the server reads Claude's client details from a URL Anthropic hosts (Client ID Metadata Document). Nothing to set up; the server must support it.
+* **No client ID — register one automatically**: Claude registers OAuth clients with the server as users connect (Dynamic Client Registration). Works with most servers, but adds client registrations over time.
+* **Use your own OAuth client**: enter a client ID you registered with the server. Leave the secret blank unless your authorization server requires one. See [Authentication for connectors](/docs/connectors/building/authentication).
+
+**Request headers**: fixed credentials such as API keys, sent on every request. See [Authenticating with request headers](#authenticating-with-request-headers).
+
+**Advanced > Transport**: set from the URL automatically; a URL ending in `/sse` selects the older SSE transport. Change it only if the server's documentation says to.
+
 ## Authenticating with request headers
 
 <Note>
-  Request header authentication is in beta. This feature is being slowly rolled out to customers; contact Anthropic for early access.
+  Request header authentication is in beta and available to a limited set of organizations. If you don't see the **Request headers** section in the Add custom connector dialog, your organization doesn't have access yet.
 </Note>
 
 If your MCP server authenticates with an API key, bearer token, or other fixed credential instead of OAuth, you can configure it in the **Request headers** section of the Add custom connector dialog. Claude stores each header value securely, does not show it again after you save, and sends it on every request to your server.

 
 ## Managing connectors
 
-To remove or edit connectors:
+To edit a connector's name or URL, or to remove a connector:
 
-1. Go to **Customize > Connectors**
+1. Go to **Customize > Connectors** (Team and Enterprise owners: **Admin settings > Connectors**)
 2. Click "Remove" or select the three-dot menu
-3. Follow prompts to edit or remove
+3. Follow the prompts
+
+Authentication settings (OAuth credentials and request headers) can't be changed after a connector is added. To change them, remove the connector and add it again with the new details. Members will need to reconnect.
 
 ## Security and privacy