Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One capture · claude-docs

One read of Claude Documentationclaude-docs-20261026T203708Z

2 pages moved out of 280 read.

Pages moved 2 significant first
Pages read 280 in this capture
Captured 20:37 UTC
Corpus hash 8f969df6781c corpus-hash

What this read moved

1-2 of 2

claude-tag/admins/connections/atlassian Changed · +4 / -6 lines

from line 36
3636 
3737## Connect a token with scopes through the Atlassian gateway
3838 
39If your organization requires tokens with scopes, connect through the gateway instead of the **Jira & Confluence** entry. Add the gateway connector inside a new bundle. A new bundle applies nowhere until you add places to it, so you can limit the token to your site's paths before any channel can use it.
39If your organization requires tokens with scopes, connect through the gateway instead of the **Jira & Confluence** entry. Add the gateway connector inside a new bundle. A new bundle applies nowhere until you add places to it, so no channel can use the token until you choose where it applies.
4040 
4141**1. Create a bundle for the gateway**
4242 
from line 44
4444 
4545**2. Add the gateway connector**
4646 
47Under **What's in it**, click **Add**, select **Connector**, and select **Custom connector**. In the [custom connector](https://claude.com/docs/claude-tag/admins/connections/custom.md) form, enter a **Name**, choose the **Basic** credential type, enter the dedicated account's email as the **Username** and the API token as the **Password**, and enter `api.atlassian.com` under **Allowed websites**. Click **Connect** to save the connector.
47Under **What's in it**, click **Add**, select **Connector**, and select **Custom connector**. In the [custom connector](https://claude.com/docs/claude-tag/admins/connections/custom.md) form, enter a **Name**, choose the **Basic** credential type, enter the dedicated account's email as the **Username** and the API token as the **Password**, and enter `api.atlassian.com` under **Allowed websites**.
4848 
49**3. Limit the credential to your site's paths**
49Under **Path prefixes**, add `/ex/jira/<cloud-id>/` and `/ex/confluence/<cloud-id>/`, using the same cloud ID in both, in lowercase. Find your cloud ID at `https://<your-site>.atlassian.net/_edge/tenant_info`. The cloud ID in a gateway request's path chooses which Atlassian site the request reaches, so a connector on this host can't be saved without path prefixes for one site, even though the form marks the field optional. Click **Connect** to save the connector.
5050 
51Under **What's in it**, open the menu on the new connector's row and click **Edit**. In the **Edit connection** dialog, add `/ex/jira/<cloud-id>/` and `/ex/confluence/<cloud-id>/` under **Path prefixes**, then click **Save**. The cloud ID in a gateway request's path chooses which Atlassian site the request reaches.
52 
53**4. Choose where the bundle applies**
51**3. Choose where the bundle applies**
5452 
5553Under **Where it applies**, click **Add place**, choose a workspace or channel under **Where**, and click **Add**. Click **Save changes** to save the places.
5654 

claude-tag/admins/connections/custom Changed · +1 / -1 lines

from line 31
3131| **Name** | A label for this connector (for example "Internal billing API") |
3232| **Credential type** | Pick the type that matches how the API authenticates; see [Credential types](#credential-types) |
3333| **Allowed websites** | The API's host (for example `api.example.com`). A wildcard is allowed as the leftmost label. You can't enter `*` alone here; a credential is always limited to specific hosts (see [Allow all hosts](https://claude.com/docs/claude-tag/admins/add-connections.md#allow-all-hosts)). The credential is sent only to hosts you list here. |
34| **Path prefixes** (optional) | Restrict the credential to specific URL paths under the host. For the MCP Connector type, shown only when the provider you pick doesn't fix its own hosts and paths. |
34| **Path prefixes** (optional) | Restrict the credential to specific URL paths under the host. Required for `api.atlassian.com`; see [Connect a token with scopes through the Atlassian gateway](https://claude.com/docs/claude-tag/admins/connections/atlassian.md#connect-a-token-with-scopes-through-the-atlassian-gateway). For the MCP Connector type, shown only when the provider you pick doesn't fix its own hosts and paths. |
3535| **Custom headers** | Any extra headers the API requires beyond the credential. Shown only for the Bearer credential type. |
3636 
3737After saving, where the credential has an allow rule, you can narrow it by HTTP method and path from its **Edit connection** dialog, opened from **Edit** in the credential's row menu on the connector's page; see [Restrict by path or method](https://claude.com/docs/claude-tag/admins/add-connections.md#restrict-by-path-or-method). To narrow a credential before any channel can use it, add the connector to a new [bundle](https://claude.com/docs/claude-tag/admins/add-connections.md#create-a-bundle), select **Edit** from the menu on its row under **What's in it**, and add the bundle's places last.
Feedback