One read of Claude Documentationclaude-docs-20260926T053713Z
18 pages moved out of 255 read.
Pages moved
18
significant first
Pages read
255
in this capture
Captured
05:37 UTC
Corpus hash
728b11e0f719
corpus-hash
What this read moved
1-18 of 18claude-tag/admins/add-connections Changed · +15 / -11 lines
from line 165
165165
166166For a custom connection, choose the credential type:
167167
168| Credential type | Use for |
169| :------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
170| Bearer | API keys and OAuth bearer tokens. Most SaaS REST APIs. |
171| Basic | HTTP Basic authentication. |
172| Body parameter | A token the API expects in the request body or query string instead of a header. |
173| AWS SigV4 | Signed requests to AWS service endpoints with an access key pair. |
174| GCP access token (with Service Account Key) | Google Cloud APIs via a service-account JSON key. Google Workspace services like Drive and Calendar also use this; see [the Google guide](/docs/claude-tag/admins/connections/google). |
175| GCP IAP (with Service Account Key) | Google Cloud services behind Identity-Aware Proxy. |
176| OAuth 2.0 JWT bearer | Server-to-server OAuth. |
177| OAuth 2.0 client credentials | Server-to-server OAuth. Salesforce uses this. |
178| MCP Connector | Sign in once as an admin; the agent acts as that account. |
168| Credential type | Use for |
169| :------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
170| Bearer | API keys and OAuth bearer tokens. Most SaaS REST APIs. |
171| Basic | HTTP Basic authentication. |
172| Body parameter | A token the API expects in the request body or query string instead of a header. |
173| AWS SigV4 | Signed requests to AWS service endpoints with an access key pair. |
174| GCP access token (with Service Account Key) | Google Cloud APIs via a service-account JSON key. Google Workspace services like Drive and Calendar also use this; see [the Google guide](/docs/claude-tag/admins/connections/google). |
175| GCP IAP (with Service Account Key) | Google Cloud services behind Identity-Aware Proxy. |
176| OAuth 2.0 JWT bearer | Server-to-server OAuth. |
177| OAuth 2.0 client credentials | Server-to-server OAuth. Salesforce uses this. |
178| MCP Connector | Sign in once as an admin; the agent acts as that account. The picker offers a fixed set of providers plus the [remote MCP connectors](/docs/connectors/custom/add-unlisted) your organization has added on claude.ai. Other OAuth APIs can't be connected this way. |
179179
180180For GitHub repositories, use the GitHub connection at [Configure GitHub access](/docs/claude-tag/admins/configure-github) rather than a credential from this table.
181181
from line 193
193193
194194List the hosts a connection's credential may be sent to. A wildcard works only as the leftmost label, like `*.example.com`; it covers subdomains at any depth but not `example.com` itself. You can't enter `*` alone here; a credential is always limited to specific hosts. To let Claude reach any host without a credential, see [Allow all hosts](#allow-all-hosts).
195195
196<Note>You can't save a connection whose **Allowed websites** include an `anthropic.com`, `claude.ai`, or `claude.com` host, such as `api.anthropic.com`.</Note>
197
196198To change a connection's name or allowed websites after saving, open the **⋮** menu on that connection's row in the bundle's **Credentials** tab and choose **Edit**; the **Edit connection** dialog labels the field **Allowed hosts**. The same menu has **Rotate secret** (where the credential type supports it) and **Delete**.
197199
198200Check the host against your account's region before saving. Some presets fill a default host that may not match your account's region; a Datadog key, for example, only works against your account's Datadog site, like `api.datadoghq.com` or `api.datadoghq.eu`.
201
202Where the connection form has a **Test connection** button, the test can check the preset's default host rather than the one you entered, so a key for a regional or self-hosted instance can fail the test and still work. Replace the prefilled host with your service's API host rather than adding yours alongside it. You can save the connection even if the test fails, and the credential is sent only to the hosts you listed.
199203
200204### Restrict by path or method
201205
claude-tag/admins/audit Changed · +6 / -6 lines
from line 8
88
99Use this page to review what Claude Tag is doing across your organization: which routines are scheduled, what memory it has saved, and where to find a record of each action it took.
1010
11<Note>The Audit page opens for Owners in your Claude organization; the other trails on this page are visible to anyone with access to the underlying surface.</Note>
11The Audit page opens for Owners in your Claude organization. The other trails on this page are visible to anyone with access to the underlying surface.
1212
1313Claude Tag activity is auditable in four places:
1414
from line 21
2121
2222The Audit page, labeled **Activity** in the admin console's left nav and page heading, at [`claude.ai/admin-settings/claude-tag/audit`](https://claude.ai/admin-settings/claude-tag/audit) has these tabs:
2323
24| Tab | What it shows |
25| :----------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
26| **Scheduled work** | Every routine across your organization, with a **Scope** filter and a per-row **⋮** menu (View details, Pause/Resume, Delete) |
27| **Memory** | Each scope's memory files, where you can read what Claude has saved for that workspace or channel. Owners can also edit or delete entries there. |
28| **Network events** | An hourly JSON export of outbound calls Claude made through Agent Proxy. Git and MCP traffic are not included in this export. Select a date and hour to download. |
24| Tab | What it shows |
25| :----------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
26| **Scheduled work** | Every routine across your organization, with a **Scope** filter and a per-row **⋮** menu (View details, Pause/Resume, Delete) |
27| **Memory** | Each scope's memory files, where you can read what Claude has saved for that workspace or channel. Owners can also edit or delete entries there. |
28| **Network events** | An hourly JSON export of the outbound requests Claude made through [Agent Proxy](/docs/claude-tag/concepts/agent-identity#agent-proxy). Git and MCP traffic are not included. Select a date and hour to download. |
2929
3030Each routine on the **Scheduled work** tab shows **Created by** (the member who set it up) in its **View details** dialog. There is no per-action log of every task and who asked; for that, use the trails below.
3131
claude-tag/admins/connections/bigquery Changed · +20 / -0 lines
## Allow the connection through a VPC Service Controls perimeter ### What the VPC Service Controls ingress rule allows
from line 54
5454@Claude how many rows are in <dataset>.<table>?
5555```
5656
57## Allow the connection through a VPC Service Controls perimeter
58
59If the Google Cloud project that holds your BigQuery data is inside a [VPC Service Controls](https://cloud.google.com/vpc-service-controls/docs/overview) perimeter, Claude's queries fail with `Request is prohibited by organization's policy` and a `vpcServiceControlsUniqueIdentifier` in the error details. To let them through, add an ingress rule that admits the [service account you created for Claude](#create-the-credential-in-google-cloud).
60
61If you allowlist [Anthropic's published egress IP range](/docs/claude-tag/admins/network-requirements) in an access level, Claude's queries still fail, because they reach your perimeter from inside Google Cloud rather than from that range. The source your perimeter sees is a Google Cloud project that Anthropic owns and can change without notice, so don't admit that project by its number.
62
63Add an [ingress rule](https://cloud.google.com/vpc-service-controls/docs/ingress-egress-rules) to the perimeter with these settings:
64
65* For the identity, admit the service account you created for Claude.
66* For the source, allow any source (an access level of `*`).
67* For the target, allow the BigQuery API (`bigquery.googleapis.com`) on the project inside the perimeter.
68
69To confirm the rule works, ask Claude to run the query that failed. The query returns results.
70
71### What the VPC Service Controls ingress rule allows
72
73The ingress rule lets requests authenticated as the service account you created for Claude cross the perimeter, and only to reach BigQuery in the project the rule names. It doesn't give the service account access to any data. The [dataset roles you granted](#grant-access-to-specific-datasets) still decide which datasets Claude can read, so keep those grants narrow.
74
75Once the connection works, delete the key file that Google Cloud downloaded to your machine when you created the key. With this rule in place, the perimeter doesn't stop a leaked key for this service account, because a request authenticated with any of the account's valid keys passes the rule from any source. [Agent Proxy](/docs/claude-tag/concepts/agent-identity#agent-proxy) holds the key you uploaded and Claude never sees it. To limit that risk further, don't create more keys for the service account.
76
5777## Related resources
5878
5979* [What this connection adds](/docs/claude-tag/users/use-cases/answer-data-questions): warehouse questions answered with charts in the thread
claude-tag/admins/connections/custom Changed · +11 / -11 lines
from line 34
3434
3535### Credential types
3636
37| Type | Use for |
38| :---------------------------------------------- | :---------------------------------------------------------------------------------------------------------- |
39| **Bearer** | An API key or token sent as `Authorization: Bearer <token>`. Most SaaS REST APIs. |
40| **Basic** | HTTP Basic authentication (`Authorization: Basic <base64(user:password)>`) |
41| **Body parameter** | A token the API expects in the request body or query string instead of a header |
42| **AWS SigV4** | AWS service APIs on `amazonaws.com` endpoints that require Signature Version 4 signing |
43| **GCP access token (with Service Account Key)** | Google Cloud APIs; the proxy exchanges the SA key for an access token |
44| **GCP IAP (with Service Account Key)** | Google Cloud services behind Identity-Aware Proxy |
45| **OAuth 2.0 JWT bearer** | APIs that accept a JWT signed with your private key in exchange for an access token (DocuSign, for example) |
46| **OAuth 2.0 client credentials** | Machine-to-machine OAuth with a client ID and secret |
47| **MCP Connector** | OAuth sign-in. Sign in once as an admin; the agent acts as that account. |
37| Type | Use for |
38| :---------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
39| **Bearer** | An API key or token sent as `Authorization: Bearer <token>`. Most SaaS REST APIs. |
40| **Basic** | HTTP Basic authentication (`Authorization: Basic <base64(user:password)>`) |
41| **Body parameter** | A token the API expects in the request body or query string instead of a header |
42| **AWS SigV4** | AWS service APIs on `amazonaws.com` endpoints that require Signature Version 4 signing |
43| **GCP access token (with Service Account Key)** | Google Cloud APIs; the proxy exchanges the SA key for an access token |
44| **GCP IAP (with Service Account Key)** | Google Cloud services behind Identity-Aware Proxy |
45| **OAuth 2.0 JWT bearer** | APIs that accept a JWT signed with your private key in exchange for an access token (DocuSign, for example) |
46| **OAuth 2.0 client credentials** | Machine-to-machine OAuth with a client ID and secret |
47| **MCP Connector** | OAuth sign-in to one of the providers in the picker or to a [remote MCP connector](/docs/connectors/custom/add-unlisted) your organization has added on claude.ai. Sign in once as an admin; the agent acts as that account. Other OAuth APIs can't be connected this way. |
4848
4949<Note>The **MCP Connector** type signs in to a connector from your organization's connector library. If you register a new connector from this form with **Add custom connector…**, that connector is added to the library on the **Connectors** page at [`claude.ai/admin-settings/connectors`](https://claude.ai/admin-settings/connectors), not only to the bundle. Removing the connection from the bundle later leaves the library entry in place.</Note>
5050
claude-tag/admins/for-slack-admins Changed · +4 / -3 lines
from line 12
1212
1313Claude reads and posts only in channels it has been added to, and in direct messages. Any workspace member who opens a direct message with Claude receives its welcome message, whether or not they've linked a Claude account. Installing the app does not add it to any channel.
1414
15A member can add Claude to a channel in one of two ways:
15A member can add Claude to a channel in any of these ways:
1616
1717* Invite it with `/invite @Claude` in the channel
1818* Select **Add to channel** on a channel Claude suggests in a direct message. Claude's welcome message, the introduction it posts when a member first opens a direct message with it, suggests public channels this way.
19* Select **Approve and post** on a message Claude drafts in a direct message for a public channel it isn't a member of. When the member approves, Claude posts the message and joins that channel. [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels) covers the flow.
1920
2021A Claude organization admin can also set [auto-join channel patterns](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name), so Claude joins a public channel whose name matches when the channel is created or renamed.
2122
22When a member selects **Add to channel** or an auto-join pattern matches, Claude adds itself to that channel using its `channels:join` scope. Slack's audit log records the join as the Claude app, with no inviter shown; neither the member's selection nor the matched pattern is visible in Slack's log. If you see a join in the audit log that no one can explain, a member selected one of these buttons or an auto-join pattern matched. Outside those two paths, Claude does not join channels on its own.
23When a member selects **Add to channel** or **Approve and post**, or an auto-join pattern matches, Claude adds itself to that channel using its `channels:join` scope. Slack's audit log records the join as the Claude app, with no inviter shown; neither the member's selection nor the matched pattern is visible in Slack's log. If you see a join in the audit log that no one can explain, a member selected one of these buttons or an auto-join pattern matched. Outside these paths, Claude does not join channels on its own.
2324
2425Reading a channel's full history requires being added there. Workspace search can surface public-channel content, the same as any app with the search scope.
2526
from line 32
3132
3233Two scopes a Slack admin commonly asks about:
3334
34* `channels:join` lets Claude add itself to a public channel when a member selects one of its suggested-channel buttons, or when the channel's name matches an [auto-join channel pattern](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name) an admin set. It cannot join private channels this way.
35* `channels:join` lets Claude add itself to a public channel when a member selects one of its suggested-channel buttons, when a member approves a message it drafted in a direct message for that channel, or when the channel's name matches an [auto-join channel pattern](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name) an admin set. It cannot join private channels this way.
3536* `users:read.email` lets Claude read a member's profile email. Claude uses it for checks such as the email domain when a member connects their Claude account. It does not connect accounts; a member still runs the Connect step in Slack.
3637
3738## What installing does not grant
claude-tag/admins/restrict-access Changed · +9 / -9 lines
from line 120
120120DMs, guest channels, and shared channels sit outside the per-scope switches:
121121
122122* **DMs.** The per-scope switches don't cover them. To close those off too, turn off the [**Allow direct messages**](#allow-or-disable-direct-messages) toggle.
123* **Guest channels.** By default Claude is off in any channel that includes a Slack guest. If a chosen channel has guests, also set [Allow Claude to work in channels with guests](#restrict-guest-channels) to **Allow** or **Channel only** on its scope.
123* **Guest channels.** By default Claude is off in any channel that includes a Slack guest. If a chosen channel has guests, also set [**How should Claude work in channels with guests**](#restrict-guest-channels) to **Full access** or **Channel only** on its scope.
124124* **Shared channels.** A [channel shared across workspaces in your Enterprise Grid](#channels-shared-across-workspaces-in-your-enterprise-grid) takes its settings from **Default Slack access** only and can't serve as a chosen channel. Claude doesn't work in a [Slack Connect channel](#slack-connect-channels), one shared with another company.
125125
126126To control who can use Claude in the allowed channels, turn on the [restriction toggle](#restrict-who-can-use-claude); to cap what a channel spends, [set a per-channel spend limit](#set-spend-limits).
from line 142
142142
143143### Restrict guest channels
144144
145By default, Claude is disabled in any channel that includes a Slack guest. You can change this default per scope with the **Allow Claude to work in channels with guests** setting, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → the scope → the collapsed **Advanced** section. The setting has three values:
145By default, Claude is disabled in any channel that includes a Slack guest. You can change this default per scope with the **How should Claude work in channels with guests** setting, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → the scope → the collapsed **Advanced** section. The setting has three values:
146146
147147| Value | What Claude does in a channel that includes a guest |
148148| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
149149| **Restrict** (default) | Doesn't reply. When someone mentions it, Claude posts a short notice that it doesn't respond in channels that include guests, with a link to this setting. |
150150| **Channel only** | Replies, but while a guest is present it runs with [channel-only access](#how-channel-only-works). The channel's own instructions still apply. |
151| **Allow** | Replies with the full access the scope gives it. Bundles, connections, and instructions from the workspace and from **Default Slack access** apply, along with repositories, memory, and skills. |
151| **Full access** | Replies with the full access the scope gives it. Bundles, connections, and instructions from the workspace and from **Default Slack access** apply, along with repositories, memory, and skills. |
152152
153A channel without its own value shows **Inherit** and takes the value from its workspace, or from **Default Slack access**. Only an organization Owner can choose **Allow** or set a scope back to **Inherit**. The setting applies to every guest channel the scope covers. To open one channel rather than a whole workspace, set it on the channel's own scope.
153A channel without its own value shows **Inherit** and takes the value from its workspace, or from **Default Slack access**. Only an organization Owner can choose **Full access** or set a scope back to **Inherit**. The setting applies to every guest channel the scope covers. To open one channel rather than a whole workspace, set it on the channel's own scope.
154154
155155Under every value, guests in the channel can read what Claude posts there.
156156
157In any channel that includes a guest, even under **Allow**, Claude won't search the workspace, look up people or channels, or read channels other than the one it's in. The results could include content the guests can't see in Slack, which is also why Claude doesn't search private channels. To have Claude search, look someone up, or read another channel, ask from a channel without guests.
157In any channel that includes a guest, even under **Full access**, Claude won't search the workspace, look up people or channels, or read channels other than the one it's in. The results could include content the guests can't see in Slack, which is also why Claude doesn't search private channels. To have Claude search, look someone up, or read another channel, ask from a channel without guests.
158158
159159#### How Channel only works
160160
from line 167
167167* No memory, including this channel's own, and no skills.
168168* No [environment set on the scope](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope). The session runs on the standard environment, so the setup script, environment variables, and network access level of the environment you chose don't apply while a guest is present.
169169
170Claude decides which access applies when a conversation starts. When no guest is in the channel, new conversations get full access, as under **Allow**.
170Claude decides which access applies when a conversation starts. When no guest is in the channel, new conversations get the same access as under **Full access**.
171171
172172A conversation that was underway before the first guest joined doesn't keep its full access. The next message from a workspace member in that thread starts the conversation over with channel-only access. A guest who writes there before a member does gets the same notice as under **Restrict**.
173173
from line 216
216216
217217What happens in a channel shared across more than one workspace inside your Enterprise Grid depends on whether every workspace in it is connected to the same Claude organization.
218218
219When the workspaces all belong to your one Claude organization, Claude replies in the channel, but only with the access and settings on your organization's [Default Slack access](/docs/claude-tag/admins/attach-to-scope) scope. Bundles, instructions, and memory set on a workspace or on that channel don't reach it. Claude posts a notice in the thread explaining this, about once a month per channel at most rather than on every reply. Where guest access is at its default **Restrict**, the [guest check](#restrict-guest-channels) still runs first and can refuse the reply.
219When the workspaces all belong to your one Claude organization, Claude replies in the channel, but only with the access and settings on your organization's [Default Slack access](/docs/claude-tag/admins/attach-to-scope) scope. Bundles, instructions, and memory set on a workspace or on that channel don't reach it. Claude posts a notice in the thread explaining these limits, but not on every reply. Where guest access is at its default **Restrict**, the [guest check](#restrict-guest-channels) still runs first and can refuse the reply.
220220
221221When the workspaces belong to different Claude organizations, each with its own settings and plan, Claude won't reply and posts a refusal message instead.
222222
from line 261
261261
262262### What a channel manager can do on the Configure page
263263
264A channel manager has to be a member of the channel in Slack. The channel's [Configure page](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), reached from the **Configure** link in any Claude reply, is split into tabs. In a channel you assigned to them, a channel manager sees the **Default model** card on the **General** tab and the repository and access bundle cards on the **Tools and access** tab. Members without the role don't see those cards. Owners and Admins also see an **Admin** tab, whose **Channel settings** card holds some of the channel scope's settings from admin settings.
264A channel manager has to be a member of the channel in Slack. The channel's [Configure page](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), which opens on claude.ai from the **Configure** link in any Claude reply, is split into tabs. In a channel you assigned to them, a channel manager sees the **Default model** card on the **General** tab and the repository and access bundle cards on the **Tools and access** tab. Members without the role don't see those cards. Owners and Admins also see an **Admin** tab, whose **Channel settings** card holds some of the channel scope's settings from admin settings.
265265
266266| Setting | What a channel manager can do |
267267| :----------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
claude-tag/admins/troubleshooting Changed · +81 / -27 lines
### This workspace is connected to a different Claude organization ### Claude is silent everywhere in the workspace
from line 27
2727| A pairing code | A message about guests, or about the channel being shared across workspaces | Send `@Claude connect` again in a channel with no guests that belongs to a single workspace. Match the exact message in [Guest and shared channels](#guest-and-shared-channels) for the fix that fits it. |
2828| The console to accept your pairing code | "Claim code is invalid, expired, or already used" | Codes are single-use and last 15 minutes. Send `@Claude connect` again and paste the fresh code right away. See [Claim code is invalid, expired, or already used](#claim-code-invalid). |
2929| The console to accept your pairing code | "Already connected to a different organization" | The workspace is paired to another Claude organization, often a trial org. See [Already connected to a different organization](#already-connected-to-a-different-organization). |
30| Your Claude account to connect after you select **Connect Claude account** | The browser page refuses the connection, and Claude DMs you "This workspace is connected to a different Claude organization" | The Claude account belongs to a different organization than the one the workspace is paired with. Connect an account from that organization; if the browser is signed in to another Claude account, sign out at claude.ai first. See [This workspace is connected to a different Claude organization](#this-workspace-is-connected-to-a-different-claude-organization). |
3031| The spend limit picker on the **Launch Claude Tag** step | A **Buy usage credits** step | Your organization pays by card in US dollars and has no credits loaded. Load credits, or select **Skip** to continue without; nothing runs in channels until the balance is funded. Invoiced organizations and those billing in other currencies see the spend limit picker regardless of balance. |
3132| A reply from Claude while you're still in setup | "Claude is disabled in this channel. Your admin can re-enable it here." | Claude Tag isn't turned on until you finish [Launch Claude Tag](/docs/claude-tag/admins/setup-overview#launch-claude-tag). Finish setup, then mention `@Claude` again. If the message persists after launch, see [Claude is disabled in this channel](#claude-is-disabled-in-this-channel). |
3233| The **Connect GitHub** step to list your organization's repositories | "The Claude app is installed on \[username], a personal account. Claude Tag connects to a GitHub organization. Install it on your organization instead." | The Claude GitHub App is on a personal GitHub account. Have a GitHub organization owner [install it on the organization](/docs/claude-tag/admins/configure-github#link-your-github-organization) that owns your repositories. You can skip the step and [grant repositories](/docs/claude-tag/admins/configure-github#grant-repository-access) after setup. |
from line 127
126127
127128**What it means**
128129
129**Allow Claude to work in channels with guests** is set to **Restrict** or **Channel only** for this channel's [scope](/docs/claude-tag/concepts/glossary#scope), so Claude checks the channel for guests before replying, and this install predates the `users:read` permission that check needs.
130The **How should Claude work in channels with guests** setting is set to **Restrict** or **Channel only** for this channel's [scope](/docs/claude-tag/concepts/glossary#scope), so Claude checks the channel for guests before replying, and this install predates the `users:read` permission that check needs.
130131
131132**How to resolve**
132133
from line 141
140141
141142**What it means**
142143
143Either a member selected **Add to channel** on a channel Claude suggested in a direct message, or the channel's name matches an [auto-join channel pattern](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name) an admin set, and Claude joined the public channel when it was created or renamed. Claude's welcome message, the introduction it posts when a member first opens a direct message with it, suggests a few public channels, each with an **Add to channel** button. Selecting one directs Claude to add itself to that channel.
144Claude joined the channel through one of these paths:
144145
145Claude performs that join with its own `channels:join` permission, so Slack's audit log records the join as the Claude app and shows no inviter; the member's selection is not visible in Slack's log. Outside those two paths, Claude never joins a channel unprompted. [What the Claude Slack app can access](/docs/claude-tag/admins/for-slack-admins) covers how members add it.
146* A member selected **Add to channel** on a channel Claude suggested in a direct message. Claude's welcome message, the introduction it posts when a member first opens a direct message with it, suggests a few public channels, each with an **Add to channel** button.
147* A member selected **Approve and post** on a message Claude drafted in a direct message for a public channel it wasn't a member of. When the member approves, Claude posts the message in the channel the member named and joins it. [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels) covers the flow.
148* The channel's name matches an [auto-join channel pattern](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name) an admin set, and Claude joined the public channel when it was created or renamed.
146149
150Claude performs that join with its own `channels:join` permission, so Slack's audit log records the join as the Claude app and shows no inviter; the member's selection is not visible in Slack's log. Outside these paths, Claude doesn't join a channel unprompted. [What the Claude Slack app can access](/docs/claude-tag/admins/for-slack-admins) covers how members add it.
151
147152**How to resolve**
148153
149154Nothing is misconfigured. If an auto-join pattern brought Claude in, review the patterns in the scope's **Advanced** section. If Claude shouldn't be in the channel, remove it with `/remove @Claude`, or [turn the scope's **Enable Claude Tag in this channel** switch off](/docs/claude-tag/admins/restrict-access#quiet-or-remove-claude-tag) so it stops responding there even if it's added again. If you have the single [**Enable Claude Tag** switch](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-on-the-team-plan) instead of the per-scope switches, remove Claude and add a [blocked channel pattern](/docs/claude-tag/admins/restrict-access#block-or-auto-join-channels-by-name) for the channel's name. If you want every join in the audit log attributed to a person, ask members to add Claude with `/invite @Claude` rather than the buttons; Slack records an invite as the inviting member's action.
from line 167
162167
163168> Claude doesn't respond in channels that include guests. You can remove the guests from this channel (Channel details -> Members -> filter by "guests"), or a claude.ai organization owner can allow it in Claude Tag settings under Advanced -> "Allow Claude to work in channels with guests".
164169
165In the message, "Claude Tag settings" is a link to the admin page where the guest setting described below lives. The role it names is a claude.ai organization owner, not a Slack admin.
170In the message, the setting it names is labeled **How should Claude work in channels with guests** in the admin console, and "Claude Tag settings" is a link to the admin page where the guest setting described below lives. The role it names is a claude.ai organization owner, not a Slack admin.
166171
167172**What it means**
168173
169The channel includes at least one Slack guest account, and **Allow Claude to work in channels with guests** is set to **Restrict** for this channel's scope. **Restrict** is the default.
174The channel includes at least one Slack guest account, and **How should Claude work in channels with guests** is set to **Restrict** for this channel's scope. **Restrict** is the default.
170175
171176**How to resolve**
172177
from line 178
173178Either fix works:
174179
175180* Remove the guests from the channel, or move the conversation to a channel with no guests; this changes no settings, so no other channel is affected.
176* Change **Allow Claude to work in channels with guests** for the scope covering this channel, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → the scope → the collapsed **Advanced** section. **Channel only** restores replies with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works). **Allow** restores replies with the scope's full access, and only an organization Owner can choose it. See [restrict guest channels](/docs/claude-tag/admins/restrict-access#restrict-guest-channels) for what each value exposes.
181* Change **How should Claude work in channels with guests** for the scope covering this channel, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → the scope → the collapsed **Advanced** section. **Channel only** restores replies with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works). **Full access** restores replies with the scope's full access, and only an organization Owner can choose it. See [restrict guest channels](/docs/claude-tag/admins/restrict-access#restrict-guest-channels) for what each value exposes.
177182
178183Either value applies to every guest channel that scope covers. To limit the change to one channel, set the value on the channel's own scope.
179184
180Either value restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even under **Allow**. Removing the guests restores search as well.
185Either value restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even under **Full access**. Removing the guests restores search as well.
181186
182187If the fix worked, a mention in the channel gets a reply.
183188
from line 201
196201**How to resolve**
197202
1982031. Mention Claude again; the retry usually clears it.
1992. If one channel hits this repeatedly, the membership check may be failing on an unusually large channel. Setting **Allow Claude to work in channels with guests** to **Allow** on the channel's scope removes the guest check for every channel that scope covers, which usually stops the message from recurring; weigh [what Allow exposes](#claude-doesn%E2%80%99t-respond-in-channels-that-include-guests) first.
2042. If one channel hits this repeatedly, the membership check may be failing on an unusually large channel. If you set the **How should Claude work in channels with guests** setting to **Full access** on the channel's scope, Claude skips the guest check in every channel that scope covers, so this message usually stops. Weigh [what Full access exposes](#claude-doesn%E2%80%99t-respond-in-channels-that-include-guests) first.
200205
201206### This channel is shared across multiple workspaces
202207
from line 215
210215
211216**What it means**
212217
213This message comes from the guest check, not from workspace sharing. **Allow Claude to work in channels with guests** is set to **Restrict** for this channel's scope, and the channel's membership can't be verified, most often because the channel is shared across an Enterprise Grid organization, so Claude declines.
218This message comes from the guest check, not from workspace sharing. The **How should Claude work in channels with guests** setting is set to **Restrict** for this channel's scope, and the channel's membership can't be verified, most often because the channel is shared across an Enterprise Grid organization, so Claude declines.
214219
215220**How to resolve**
216221
217Use a channel that belongs to a single workspace. Setting the scope's guest setting to **Allow** removes the guest check that posts this message, but a Grid-shared channel still doesn't behave like a single-workspace one. When its workspaces connect to different Claude organizations, Claude posts the refusal in [This channel is shared among several Claude workspaces](#this-channel-is-shared-among-several-claude-workspaces) instead of replying. When they all share your one Claude organization, Claude replies with only your organization's default access and settings, described in [This channel is shared across several Slack workspaces](#this-channel-is-shared-across-several-slack-workspaces).
222Use a channel that belongs to a single workspace. Setting the scope's guest setting to **Full access** removes the guest check that posts this message, but a Grid-shared channel still doesn't behave like a single-workspace one. When its workspaces connect to different Claude organizations, Claude posts the refusal in [This channel is shared among several Claude workspaces](#this-channel-is-shared-among-several-claude-workspaces) instead of replying. When they all share your one Claude organization, Claude replies with only your organization's default access and settings, described in [This channel is shared across several Slack workspaces](#this-channel-is-shared-across-several-slack-workspaces).
218223
219224### This channel is shared among several Claude workspaces
220225
from line 253
248253
249254The channel is shared across more than one Slack workspace, and every one of those workspaces belongs to your Claude organization. Claude works there, but only with the access and settings on your [**Default Slack access**](/docs/claude-tag/admins/attach-to-scope) scope. Bundles, instructions, and memory attached to a workspace or to this channel don't apply.
250255
251The notice posts at most about once a month per channel, so replies in this channel run under the same defaults even when no notice accompanies them.
256Claude doesn't post the notice on every reply, so replies in this channel run under the same defaults even when no notice accompanies them.
252257
253258**How to resolve**
254259
from line 347
342347 Disconnecting deletes the workspace's Claude data, including its memory, channel configurations, sessions, and the routines set up in its channels. The deletion can't be undone. See [Data lifecycle and deletion](/docs/claude-tag/concepts/data-lifecycle) for the full list of what's deleted.
343348</Warning>
344349
350### This workspace is connected to a different Claude organization
351
352**What you see**
353
354You select **Connect Claude account** and sign in, but the browser page refuses the connection and names the organization mismatch. Claude also DMs you:
355
356> **This workspace is connected to a different Claude organization**
357>
358> Sign in with an account from that organization and click **Connect Claude account** again. To use your organization here instead, ask a Slack workspace admin.
359>
360> Signed in to a different Claude account in your browser? Sign out at claude.ai first, then click **Connect Claude account**.
361
362If the workspace is covered by an [Enterprise Grid pairing](/docs/claude-tag/admins/workspaces#pair-an-enterprise-grid) rather than paired on its own, the DM is instead titled **This workspace isn't set up for your Claude organization yet** and adds that a Slack admin of the workspace can run `@Claude connect` to pair that one workspace with your organization.
363
364**What it means**
365
366The Claude account you signed in with belongs to a different Claude organization than the one this Slack workspace is paired with, so Claude refused the connection and left nothing connected. The connect flow uses whichever Claude account your browser is already signed in to, which may not be the account you meant to connect.
367
368If instead the console rejected a workspace pairing code during setup, see [Already connected to a different organization](#already-connected-to-a-different-organization) rather than this entry.
369
370**How to resolve**
371
372Connect a Claude account that belongs to the organization your Slack workspace is paired with:
373
3741. If your browser is signed in to a different Claude account, sign out at [claude.ai](https://claude.ai).
3752. DM `@Claude`.
3763. Select **Connect Claude account**.
3774. Sign in with an account from the paired organization.
378
345379<a id="claim-code-invalid" />
346380
347381### Claim code is invalid, expired, or already used
from line 394
360394
361395## Nothing responds
362396
363Most of the silence problems in this section span a whole workspace or channel and come down to configuration. If Claude stays silent in one thread but answers everywhere else, a setting isn't the cause. Either Claude's session for that thread is stuck, or the thread is muted. See [Claude went silent in one thread, but responds elsewhere](#claude-went-silent-in-one-thread-but-responds-elsewhere).
397Most of the silence problems in this section span a whole workspace or channel and come down to the app's authorization or configuration. If Claude stays silent in one thread but answers everywhere else, a setting isn't the cause. Either Claude's session for that thread is stuck, or the thread is muted. See [Claude went silent in one thread, but responds elsewhere](#claude-went-silent-in-one-thread-but-responds-elsewhere).
364398
365399### Claude went silent in one thread, but responds elsewhere
366400
from line 408
374408
375409To bring Claude back to a muted thread, send `@Claude !unmute` in the thread or @-mention Claude there, as [Thumbs-down reactions and muting](/docs/claude-tag/users/commands#thumbs-down-reactions-and-muting) describes.
376410
377Without that notice, the session behind that thread is stuck: it hasn't replied and hasn't posted an error. Because Claude responds everywhere else, the problem is confined to that one session, and none of the configuration fixes in the entries below apply.
411Without that notice, the session behind that thread is stuck: it hasn't replied and hasn't posted an error. Because Claude responds everywhere else, the problem is confined to that one session, and none of the workspace-level fixes in the entries below apply.
378412
379413**How to resolve**
380414
from line 418
384418
385419If the same request stalls again on the fresh session, send [feedback](/docs/claude-tag/users/commands#send-feedback) from that thread so Anthropic can investigate.
386420
421### Claude is silent everywhere in the workspace
422
423**What you see**
424
425Mentions get no reaction and no reply in every channel and DM in the workspace, and nothing was changed on the Claude side.
426
427**What it means**
428
429Slack can revoke the Claude app's authorization for a workspace without any admin action and with no change on the Claude side.
430
431On Enterprise Grid, the organization-level install can lose its authorization the same way, and then every workspace in the Grid goes silent. See [Claude is silent everywhere on Enterprise Grid](#claude-is-silent-everywhere-on-enterprise-grid).
432
433**How to resolve**
434
435Reinstall the Claude app over the existing install to restore the lost authorization. Don't uninstall first, because uninstalling [deletes the workspace's Claude data](/docs/claude-tag/concepts/data-lifecycle#actions-in-slack).
436
4371. As a Slack workspace admin, open [Claude for Slack](https://claude.com/claude-for-slack) and select **Add to Slack**.
4382. Approve the consent screen Slack shows. If Slack shows **Unapproved permissions requested** instead of finishing the install, see [Unapproved permissions requested](#unapproved-permissions-requested).
4393. Mention `@Claude` anywhere in the workspace. If the reinstall worked, the mention gets a reaction and a reply. A reply that says the workspace isn't set up means the workspace needs to be paired with your Claude organization again; see [This workspace isn't set up for Claude Tag yet](#this-workspace-isn%E2%80%99t-set-up-for-claude-tag-yet).
440
387441### Claude is silent everywhere on Enterprise Grid
388442
389443**What you see**
from line 739
685739
686740When Claude can name the cause, it posts one of these instead:
687741
688| Message | Cause |
689| -------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
690| "Hit the session rate limit — try again in a few seconds." (or "in about Ns" when Claude knows the wait) | Too many sessions started at once; wait, then mention Claude again |
691| A message naming a specific repository that isn't available or isn't configured | The repository isn't granted for this channel; see [GitHub doesn't work in this channel](#github-doesn%E2%80%99t-work-in-this-channel) |
692| "That environment or repo isn't configured for Claude Code. Check claude.ai/code and try again." | The scope's pinned environment isn't set up; see [Channel sessions use the wrong environment](#channel-sessions-use-the-wrong-environment-or-can%E2%80%99t-find-one) |
693| "Claude is having trouble starting sessions right now. Try again in a minute." | The service that runs sessions is briefly unavailable; retry |
694| "You don't have permission to start a session here." | A permission check refused to start the session; when Claude knows which check failed, the message names it |
742| Message | Cause |
743| ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
744| "That message didn't get through to Claude." | Requests arrived faster than Claude accepts them at that moment; wait a few seconds, then mention Claude again |
745| A message naming a specific repository that isn't available or isn't configured | The repository isn't granted for this channel; see [GitHub doesn't work in this channel](#github-doesn%E2%80%99t-work-in-this-channel) |
746| "That environment or repo isn't configured for Claude Code. Check claude.ai/code and try again." | The scope's pinned environment isn't set up; see [Channel sessions use the wrong environment](#channel-sessions-use-the-wrong-environment-or-can%E2%80%99t-find-one) |
747| "Claude is having trouble starting sessions right now. Try again in a minute." | The service that runs sessions is briefly unavailable; retry |
748| "You don't have permission to start a session here." | A permission check refused to start the session; when Claude knows which check failed, the message names it |
695749
696750**What it means**
697751
claude-tag/admins/workspaces Changed · +33 / -4 lines
## Set up Claude Tag on Enterprise Grid ### Install the app across the Grid
from line 1
11# Manage workspaces and versions
22
3> Connect more Slack workspaces or an Enterprise Grid to Claude Tag, choose which Claude version each channel uses, and disconnect a workspace.
3> Connect more Slack workspaces or an Enterprise Grid to Claude Tag, choose which Claude Tag version each channel uses, and disconnect a workspace.
44
55export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
66
77<BetaNote />
88
9This page covers managing Slack workspace pairings after initial setup: adding more workspaces, choosing which Claude Tag version each one runs, turning Claude on or off on the Team plan, and disconnecting one.
9This page covers managing Slack workspace pairings after initial setup: adding more workspaces, installing the app and pairing across a Slack Enterprise Grid, choosing which Claude Tag version each one runs, turning Claude on or off on the Team plan, and disconnecting a workspace.
1010
1111A workspace pairing links one Slack workspace (or Enterprise Grid) to your Claude organization so `@Claude` can run there. Your first pairing was created during [setup](/docs/claude-tag/admins/setup-overview). To add more, you must be an Owner in your Claude organization, and a Workspace Admin (or Grid Org Admin) in the Slack workspace you're adding.
1212
from line 36
3636
3737**You'll see:** the new workspace in the Slack row's connected list and as a scope in the **Claude Tag's access** section.
3838
39## Set up Claude Tag on Enterprise Grid
40
41On Slack Enterprise Grid, installing the Claude app takes two Slack actions instead of one. A Slack Org Owner or Org Admin installs the app once for the entire Slack organization, then adds the installed app to each workspace where people will use Claude. After that, an Owner in your Claude organization pairs the whole Grid with a single Grid-wide pairing code.
42
43### Install the app across the Grid
44
45<Steps>
46 <Step title="Sign in to a workspace in the Grid">
47 As a Slack Org Owner or Org Admin, sign in to one of the Grid's workspaces rather than the Slack organization admin dashboard. Slack offers **Install to entire organization** only when you start from inside a workspace.
48 </Step>
49
50 <Step title="Install to the entire organization">
51 On the [Claude for Slack](https://claude.com/claude-for-slack) listing, select **Add to Slack > Install to entire organization**.
52
53 If some workspaces in the Grid already installed the app on their own, leave those installations in place and choose **Install to entire organization** anyway. Don't uninstall first, because uninstalling the app from a workspace [deletes that workspace's Claude data](/docs/claude-tag/concepts/data-lifecycle#actions-in-slack).
54 </Step>
55
56 <Step title="Add the app to each workspace">
57 From the Slack organization admin dashboard, add the Claude app to each workspace where people will use Claude. Each workspace still needs the app added before people there can invite and mention `@Claude`.
58 </Step>
59</Steps>
60
3961### Pair an Enterprise Grid
4062
41When a Grid Org Owner or Org Admin sends `@Claude connect`, the reply includes two codes. The `workspace_` code pairs only the workspace it was sent from. The `enterprise_` code pairs every workspace in the grid at once; redeem it when Claude should work across the grid.
63To get the Grid's pairing codes, a Slack Org Owner or Org Admin sends `@Claude connect`, with no other text, in a channel of any workspace in the Grid. Claude's reply includes two codes, one beginning `enterprise_` and one beginning `workspace_`. The `enterprise_` code pairs every workspace in the Grid that isn't already paired on its own. The `workspace_` code pairs only the workspace where `@Claude connect` was sent.
4264
43The choice matters for direct messages. On Enterprise Grid, DMs follow each user's home workspace rather than the workspace you paired, so pairing a single workspace leaves DMs unanswered for users homed in the grid's other workspaces. The `enterprise_` code covers them all.
65Paste the `enterprise_` code in one of these places:
66
67* **During setup:** paste the code into the **Paste the pairing code** field on the [setup page](/docs/claude-tag/admins/setup-overview#pair-your-slack-workspace)
68* **After setup:** go to [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) > **Where Claude Tag works** > the Slack row's **⋮** menu > **+ Add workspace**, and paste the code into the dialog
69
70Claude answers a direct message according to the pairing of the sender's home workspace, so only the Grid-wide pairing covers DMs from every workspace in the Grid.
71
72To move the Grid-wide pairing to a different Claude organization, an Owner in the Claude organization that holds it disconnects the Grid first. Disconnecting deletes the Claude-side data listed under [Revoke a pairing](#revoke-a-pairing) for every workspace the Grid-wide pairing covered. Messages Claude already posted stay in Slack.
4473
4574## Turn Claude Tag on or off and set the version for a scope
4675
claude-tag/concepts/how-it-works Changed · +20 / -2 lines
### What Claude can do in other channels
from line 16
1616* [Starting a session](#start-a-session), [tracking progress](#track-claude%E2%80%99s-progress), and [steering mid-thread](#reply-in-the-thread-to-steer): what to type, what to watch, and who can redirect
1717* [Team channels and personal DMs](#team-channels-and-personal-dms): which surface to use, and how access differs between them
1818* [Key concepts](#key-concepts): agent identity, scheduling, and memory defined
19* [Lifecycle of a request](#lifecycle-of-a-request): the five-step loop, [the checklist](#how-the-checklist-updates), [per-channel access](#channel-access), and [scheduled tasks](#one-off-and-scheduled-tasks)
19* [Lifecycle of a request](#lifecycle-of-a-request): the five-step loop, [the checklist](#how-the-checklist-updates), [per-channel access](#channel-access), [other channels](#what-claude-can-do-in-other-channels), and [scheduled tasks](#one-off-and-scheduled-tasks)
2020* [Session context and memory](#session-context-and-memory): what Claude reads, what survives idle, and what carries across channels
2121
2222## Walk through a Claude Tag session
from line 183
183183| A page kept current | Any of the above, edited in place over time | Digests, indexes, standing reports |
184184| A hosted page | A web page published on claude.ai, linked in the thread | Dashboards, prototypes, reports |
185185
186A hosted page stays available after the session ends, and Claude updates it when you ask in the thread. Anyone with access to the channel can open it; [artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) covers the access model. These are the same artifacts [Claude Code publishes](https://code.claude.com/docs/en/artifacts), with channel-based access in place of owner-controlled sharing.
186A hosted page stays available after the session ends, and Claude updates it when you ask in the thread. Anyone with access to the channel can open it. [Artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) covers the access model. These are the same artifacts [Claude Code publishes](https://code.claude.com/docs/en/artifacts), with channel-based access in place of owner-controlled sharing.
187187
188188For code work, the result is usually a draft pull request opened under the Claude GitHub App, with the link posted in the thread.
189189
from line 206
206206* **Ask what Claude can reach.** In any channel, `@Claude what can you access from this channel?` lists its current reach.
207207* **If Claude cannot reach something, the channel was not granted access.** Another channel may have the access, and an organization Owner can add it. [How agent identity works](/docs/claude-tag/concepts/agent-identity) covers the model.
208208* **Personal connectors are separate from channel connections.** A connection an admin attaches to a channel is separate from a connector on your personal claude.ai account. Your own connectors work in your DMs. Claude can also [use them in a channel](/docs/claude-tag/concepts/personal-connectors) for your own tasks, after you allow it.
209
210### What Claude can do in other channels
211
212A session works in the channel or DM where you asked, and it can also reach other public channels that Claude is a member of. For example, ask in `#team-eng` to "post a summary of this thread in #announcements", and Claude posts the summary in `#announcements` as a new top-level message.
213
214Where you ask decides what Claude can do in the other channel:
215
216| Where you ask | Read the other channel | Post, reply, or react there |
217| :---------------- | :------------------------------------------------- | :------------------------------------------------------------------- |
218| A public channel | Yes, unless the channel you ask in includes guests | Yes |
219| A private channel | Yes, unless the channel you ask in includes guests | No |
220| A DM with Claude | Yes | New top-level posts only, each after you select **Approve and post** |
221
222* **Attribution line**: every message Claude posts outside the conversation you asked from carries a line under it that names where it came from. When you ask in a thread, the line links back to that thread and names whoever last addressed Claude there, as in "Sent by Claude in #team-eng on behalf of @jordan". When you ask in a DM, the line names the person who approved the post, as in "Sent by Claude, approved by @jordan".
223* **Replies**: replies under a message Claude posted in another channel don't reach the session you asked in. To follow up on the original task, reply in the thread where you asked.
224* **Which channels Claude can post into**: a public channel in the same Slack workspace that Claude is already a member of. Claude can't post into a Slack Connect channel or a [channel shared across workspaces](/docs/claude-tag/admins/restrict-access#channels-shared-across-workspaces-in-your-enterprise-grid), wherever you ask from.
225* **If Claude isn't a member of the target channel**: when you ask from a channel, add Claude by sending `/invite @Claude` from inside the target channel. When you ask from a DM, approving the post adds Claude to the target channel.
226* **Channels with guests**: Claude can post into a [channel that includes guests](/docs/claude-tag/admins/restrict-access#restrict-guest-channels) only when the **How should Claude work in channels with guests** setting covering that channel is **Full access**.
209227
210228### One-off and scheduled tasks
211229
claude-tag/users/good-habits Changed · +13 / -1 lines
### Mentioning a user group
from line 24
2424
2525Claude can't add anyone to a channel, and it doesn't decide whether a mentioned person is notified. Slack's prompt to invite or notify someone who isn't in the channel appears only for messages you type yourself; it never applies to messages Claude posts. Slack delivers Claude's mention the way it delivers any app-posted message. In a public channel, the person is notified in their Activity view even though they haven't joined. In a private channel, they aren't notified and can't see the message until someone invites them. If you want someone to follow a thread Claude is working in, invite them yourself.
2626
27### Mentioning a user group
28
29Ask Claude to notify a user group, such as an on-call rotation. Claude mentions the group, and Slack notifies its members. If Claude writes the group's @handle as plain text instead of mentioning the group, Slack notifies no one, so ask Claude to notify the group rather than to include its handle.
30
31If Claude replies with re-approval guidance instead of mentioning the group, your workspace's Claude app predates a Slack permission that group mentions need. Ask a Slack admin to re-approve the app, and send them [Slack app permissions](/docs/claude-tag/admins/troubleshooting#slack-app-permissions).
32
33Claude never pings @channel, @here, or @everyone.
34
2735## Write tasks that close
2836
2937The phrasing of a task determines whether it has a verifiable end state, what form the result takes, and how Claude responds while working on it.
from line 126
118126
119127Start a new thread for each new task. The fresh session begins with full room for the work, picks up any configuration changes made since the old thread began, and keeps each piece of work reviewable on its own. A thread that accumulates many tasks eventually [grows past what one session can hold](/docs/claude-tag/users/troubleshooting#this-conversation-is-too-long-for-me-to-process).
120128
129To start several independent tasks from inside an existing thread, [ask Claude to open a thread for each](/docs/claude-tag/users/prompt-library#fan-out-work-across-threads). To continue the current discussion in a fresh thread, run [`!fork`](/docs/claude-tag/users/commands#fork-a-thread).
130
121131### Pick the right surface
122132
123133Channel access belongs to the channel, and DM access belongs to you. A channel can also be yours alone. Create one with just you and Claude in it, and it works the same way a team channel does. The table compares the three surfaces.
from line 146
136146
137147Reading a public channel's full history, rather than what search finds, needs Claude to be a member of that channel. If it says it can't read a public channel, `/invite @Claude` from inside that channel adds it.
138148
149Claude can also post into other public channels, and the rules depend on where you ask. See [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels).
150
139151A private channel is readable only from inside it. Inviting Claude lets it work in that channel, but Claude can't read the private channel's messages from any other channel or DM. To ask about a private channel, ask in that channel.
140152
141Channels in a different workspace stay out of reach. Claude also doesn't answer in a [Slack Connect channel](/docs/claude-tag/admins/restrict-access#slack-connect-channels), one shared with another company.
153Claude can't post into a channel in a different workspace, and it doesn't answer in a [Slack Connect channel](/docs/claude-tag/admins/restrict-access#slack-connect-channels), one shared with another company.
142154
143155When more than one surface would work, prefer a channel. Work that happens there compounds, because Claude can draw on it in later threads and teammates can find it, redirect it, or build on it.
144156
claude-tag/users/proactivity Changed · +13 / -5 lines
## Where a routine posts its results
from line 1
11# Set up routines
22
3> Claude Tag runs routines you set up from the channel. See scheduled jobs, channel watching, pull request subscriptions, paste-ready routine recipes, and how to list or pause standing work.
3> Claude Tag runs routines you set up from a channel. See scheduled jobs, channel watching, pull request subscriptions, where results post, and how to pause them.
44
55export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
66
from line 92
9292
9393Pair it with a weekly rollup so untagged posts are still swept; [Triage requests](/docs/claude-tag/users/use-cases/triage-requests) has both messages.
9494
95## Where a routine posts its results
96
97A routine you set up from inside a thread usually reports back in that thread each time it runs, for as long as the thread's [session](/docs/claude-tag/concepts/how-it-works#what-survives-between-replies) lasts. To keep the results in the thread, ask Claude to report back there when you set the routine up. If you send [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread, the routine moves to the thread's new session and keeps reporting there.
98
99If the thread's session [gets stuck](/docs/claude-tag/users/troubleshooting#claude-reacted-or-started-thinking-then-never-replied), the routine doesn't move to the session that replaces it, and its later runs usually post at the channel's top level instead. To bring the results back into a thread, disable the routine and set it up again from that thread.
100
101For a routine you set up at the channel's top level, Claude usually announces each run in a short top-level message and does the work in the thread under it. To follow up on any routine post, mention `@Claude` in a reply under it.
102
95103## Manage standing work
96104
97Anyone in the channel can list, edit, or disable its standing work:
105Anyone in the channel can manage its standing work:
98106
99107* **List.** Ask "what routines do you have set up in this channel?", or send [`@Claude !routines`](/docs/claude-tag/users/commands#list-the-routines-in-a-channel). Add a channel mention or its ID, as in `@Claude !routines #other-channel`, to list another channel's routines; pick the channel from Slack's autocomplete so it lands as a real mention, since a typed name on its own isn't accepted.
100* **Edit.** Describe the change and it updates the job
101* **Disable.** Name the job to stop, as in "disable the Friday rollup"
108* **Reschedule, pause, or stop a routine.** Name the routine and the change, as in "disable the Friday rollup" or "move the standup summary to 10am Pacific"
109* **Change what a routine does.** Ask Claude to stop the routine, then set up a replacement from the channel where the results should post.
102110
103111Standing work is visible to the channel: jobs post into the channel they belong to, or into another public channel you name that Claude has been added to. A channel's routines keep running if their creator leaves the channel, is removed from your Claude organization, or has their Slack account deactivated, and anyone still in the channel can disable them. Routines a person set up in a direct message with Claude belong to that person's account and are turned off when the person is removed from your Claude organization.
104112
from line 114
106114
107115* A job runs with the channel's connections, the same as an interactive request.
108116* Claude can post a job's output into another public channel in the same workspace only if the job's own channel is public and Claude has been added to the target channel. It labels the message with the channel it came from.
109* Claude doesn't post job output to private channels, DMs, group DMs, or externally shared channels, and doesn't message people directly. The one exception is the completion or failure notice it sends to whoever set up the routine, and only when that person's Slack account is connected to their Claude account.
117* Claude doesn't post a job's output into a different channel that's private or externally shared, or into a DM or group DM, and doesn't message people directly. Claude does send a completion or failure notice to whoever set up the routine, when that person's Slack account is connected to their Claude account.
110118* Schedules run in UTC. Name the timezone when you set a schedule, as in "every weekday at 9am Pacific". With no timezone in your message, Claude uses the one on your Slack profile. To confirm the time Claude set, send [`@Claude !routines`](/docs/claude-tag/users/commands#list-the-routines-in-a-channel), which lists schedules in UTC.
111119* A routine runs at a fixed UTC time, so each daylight saving change shifts its local time by an hour, in the same direction the clocks move. A routine running at 9am Pacific moves to 10am after the clocks go forward, or to 8am after they go back. Ask Claude to reschedule the routine to the local time you want.
112120* A scheduled job that touches a github.com repository uses the same GitHub connection your admin set up for interactive work. See [Configure GitHub access](/docs/claude-tag/admins/configure-github#scheduled-work-uses-the-same-connection).
claude-tag/users/prompt-library Changed · +11 / -1 lines
## Fan out work across threads
from line 1
11# Prompt library
22
3> Copy-paste prompts for Claude Tag in Slack, each with why it works. See first messages, forwarded-message handoffs, channel rules, memory checks, routines, and mid-thread steering.
3> Copy-paste prompts for Claude Tag in Slack, each with why it works. See first messages, handoffs, channel rules, memory checks, routines, fan-out, and steering.
44
55export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
66
from line 115
115115```
116116
117117**Why it works**: you name which job. Any channel member can disable a scheduled job; you don't need to find an admin to stop a noisy routine.
118
119## Fan out work across threads
120
121Give Claude a list of independent tasks in a channel thread, and ask it to open one thread per task. Claude posts a top-level message for each task in the same channel, works in the replies under it, and replies in the thread where you asked with a link to each new thread.
122
123```text wrap theme={null}
124@Claude for each of these issues, start a new thread in this channel and fix it there. Open a draft PR in each, and post the links here when the threads are up.
125```
126
127**Why it works**: each new thread [runs its own session](/docs/claude-tag/users/good-habits#start-a-new-thread-for-a-new-task) in its own sandbox, so the tasks run at the same time and you can review each one on its own. To continue one existing discussion in a new thread instead, use [`!fork`](/docs/claude-tag/users/commands#fork-a-thread).
118128
119129## Steer work mid-thread
120130
claude-tag/users/troubleshooting Changed · +79 / -11 lines
### Claude replies in a channel without an @-mention ### I want Claude to remove a message it posted
from line 30
30302. **Is Claude in this channel?** Type `/invite @Claude` in the channel's message box, not in a thread reply. Slack rejects `/invite` inside threads ("/invite is not supported in threads. Sorry!"). **Works**: Slack posts "Claude was added to #channel" (or "is already in this channel"). Mention it again. **Fails**: Slack says you can't add apps to this channel (a Slack Connect or guest-restricted channel); try an internal channel instead. If Slack says "You don't have permission to invite people to this channel", the channel or workspace limits who can add people. In Slack, open **Channel details** → **Agents & apps** (called **Integrations** in some Slack versions), select **Add**, and pick **Claude**. Or ask someone who can add people to the channel to add Claude.
31313. **Is Claude Tag turned on for this channel?** Mention it again now that it's invited. **Works**: it reacts and replies. **Fails**: it replies "Claude is disabled in this channel" (Claude Tag is turned off for the channel, its workspace, or the organization), or it replies but behaves like the earlier Claude in Slack, with no channel memory and pull requests opening under your name rather than Claude's (the channel is set to **Legacy**). Either way this needs your admin (send them [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/restrict-access#migrate-from-the-earlier-claude-in-slack)).
3232
33If `@Claude` still gets no reaction and no reply after all three, send your admin [the admin entries for a silent workspace](/docs/claude-tag/admins/troubleshooting#nothing-responds). If the silence covers every channel across an Enterprise Grid, the fix needs a Slack organization admin rather than your Claude admin, so send the link to them.
33If `@Claude` still gets no reaction and no reply after all three, send the [admin entries for a silent workspace](/docs/claude-tag/admins/troubleshooting#nothing-responds) to an admin. For silence in one channel, send them to your Claude admin. For silence across a whole workspace or a whole Enterprise Grid, send them to whoever administers Slack for you, because the fix usually needs a Slack admin.
3434
3535### Claude replies to me but not to a teammate
3636
from line 196
196196
197197Reply in the thread with an instruction such as "only respond when I @-mention you"; Claude follows that instruction for the rest of the thread.
198198
199### Claude replies in a channel without an @-mention
200
201**What you see**
202
203Someone posts a top-level message in the channel without mentioning Claude, and Claude replies to it in a thread.
204
205**What it means**
206
207The channel's [**Respond automatically**](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting is on. The setting is on by default.
208
209In a channel where someone has [told Claude which kinds of untagged messages to answer](/docs/claude-tag/users/when-claude-responds#what-claude-does-with-a-channel-message), it answers those kinds as well.
210
211**How to resolve**
212
213Turn the **Respond automatically** setting off in the channel where the replies are appearing.
214
215Post `@Claude only respond in this channel when someone @-mentions you` at the channel's top level, not in a thread. Claude confirms the change, which applies to the whole channel rather than to you alone.
216
217If Claude doesn't confirm the change, turn the setting off on the channel's Configure page:
218
2191. Open the **Configure** link in the footer of any Claude reply in the channel.
2202. Turn off the **Respond automatically** toggle.
2213. Click **Save**.
222
223If the Configure page says an admin has locked the channel's settings, ask an admin to [turn automatic replies off](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) for the channel.
224
225The **Respond automatically** setting doesn't quiet a thread Claude has already posted in. To quiet one of those threads, reply in it with an instruction such as "only respond when I @-mention you".
226
199227### I want to take back something I sent
200228
201229**What you see**
from line 238
210238
211239Say so in a new reply ("ignore that, do X instead"), or start a fresh thread for a clean session.
212240
241### I want Claude to remove a message it posted
242
243**What you see**
244
245Claude posted a message in a conversation you're in, and you want it removed.
246
247**What it means**
248
249Claude can delete only messages that the conversation's current [session](/docs/claude-tag/concepts/glossary#session) posted, so it can't delete your messages, anyone else's, or a message it posted before that session started.
250
251**How to resolve**
252
253Ask in the thread where Claude posted the message ("`@Claude` delete that reply"). Claude deletes a message only when someone in the conversation explicitly asks it to.
254
255Deleting a message this way has the following effects:
256
257* The deletion is permanent.
258* When the deleted message started a thread that has replies, Slack keeps the replies.
259* Deleting the message from Slack doesn't remove it from the session's transcript. See [What Anthropic stores](/docs/claude-tag/concepts/data-lifecycle#what-anthropic-stores).
260
213261### This conversation is too long for me to process
214262
215263**What you see**
from line 575
527575
528576**What you see**
529577
530Claude posts in the thread:
578Claude posts one of these messages in the thread.
531579
580**Claude Tag spend limit**
581
532582> You've reached a Claude Tag spend limit. A Claude.ai organization owner can raise it in Claude.ai admin settings. Once the limit is raised, mention me to retry.
533583
534You may also see a heads-up before you hit the limit. It starts "Heads up — your organization has used *N%* of its monthly Claude Tag spend limit." for the organization limit, or "Heads up — this channel has used *N%* of its monthly Claude Tag spend limit." for a channel limit.
584Before you hit the limit, Claude can post a heads-up that starts "Heads up — your organization has used *N%* of its monthly Claude Tag spend limit." for the organization limit, or "Heads up — this channel has used *N%* of its monthly Claude Tag spend limit." for a channel limit.
535585
586**Your individual extra usage limit**
587
588In a DM, usage is billed to your seat. When your own extra usage limit is the cap, Claude posts:
589
590> You've reached your individual extra usage limit, so I couldn't finish this turn. A Claude.ai organization owner can raise your limit in Claude.ai admin settings (Usage), or it resets when your next usage period starts. Once either happens, mention me to retry.
591
592**Organization extra usage limit**
593
594In a DM or a channel, when your organization's extra usage limit is the cap rather than a Claude Tag spend limit, Claude posts:
595
596> Your organization has reached its extra usage spend limit, so I couldn't finish this turn. A Claude.ai organization owner can raise it in Claude.ai admin settings (Usage), or it resets when the next usage period starts. Once either happens, mention me to retry.
597
536598**What it means**
537599
538Usage hit a cap an admin set, either for the whole organization or for this channel. A rate limit looks similar but is a different problem, and raising the spend limit doesn't clear it. If your message says "Hit the session rate limit — try again in a few seconds." (or "in about Ns" when Claude knows the wait), too many sessions started at once. Wait a moment, then mention Claude again.
600Usage hit a cap. For the **Claude Tag spend limit** message, the cap is a spend limit an admin set, either for the whole organization or [for this channel](/docs/claude-tag/admins/restrict-access#set-spend-limits), and the message reads the same for both.
539601
602A rate limit looks similar but is a different problem, and raising the spend limit doesn't clear it. If your message instead says "That message didn't get through to Claude." or begins "Rate-limited delivering that message", requests arrived faster than Claude accepts them at that moment. Wait a few seconds, then send your message again.
603
540604**How to resolve**
541605
542Ask your admin to raise the limit; they do so at [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag). Your admin here is whoever manages your organization's Claude account at claude.ai, not necessarily your Slack administrator. Once the limit is raised, mention Claude in the same thread to retry.
606* For the **Claude Tag spend limit** message, ask your admin to raise the limit; they do so at [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag). Your admin here is whoever manages your organization's Claude account at claude.ai, not necessarily your Slack administrator.
607* For the **Your individual extra usage limit** and **Organization extra usage limit** messages, ask a claude.ai organization owner to raise the limit in the claude.ai admin settings under **Usage**, or wait for it to reset when the next usage period starts.
543608
609Once the limit is raised or the period resets, mention Claude in the same thread to retry.
610
544611## DMs aren't working
545612
546613DMs run on your own Claude account rather than the organization's agent. They need a seat that includes Claude Code, and they use your personal connectors rather than the channel connections. If channels work but DMs don't, first check that your Claude account is connected; DM `@Claude` and it prompts you to connect if it isn't.
from line 683
616683
617684## Related resources
618685
686* [Control when Claude Tag responds](/docs/claude-tag/users/when-claude-responds): what makes Claude reply without an @-mention, and the controls that turn those replies off
619687* [How Claude Tag works](/docs/claude-tag/concepts/how-it-works): why behavior differs by channel and thread
620688* [Give feedback](https://support.claude.com): report a bug from the thread where it happened
621689
claude-tag/admins/connections/datadog Changed · +3 / -1 lines
from line 36
3636| Claude's application key | The Application key from Datadog. Optional in the form; add it so Claude can read metrics, monitors, and dashboards |
3737| Allowed websites | Prefilled by the preset; override for other sites (see below) |
3838
39Datadog has a separate API host per site, and a key only works against its own. If your account is on a site without a picker entry, pick any Datadog entry and override Allowed websites with your site's API host: `api.us3.datadoghq.com`, `api.ap1.datadoghq.com`, or `api.ddog-gov.com`. To change the host later, open the **⋮** menu on this connection in the bundle's Credentials tab and choose **Edit**.
39Datadog has a separate API host per site, and a key only works against its own. If your account is on a site without a picker entry, pick any Datadog entry and override the **Allowed websites** field with your site's API host: `api.us3.datadoghq.com`, `api.ap1.datadoghq.com`, or `api.ddog-gov.com`. To change the host later, open the **⋮** menu on this connection in the bundle's Credentials tab and choose **Edit**.
40
41If you override the **Allowed websites** field, replace the prefilled host with your site's API host rather than adding yours alongside it, so that **Test connection** checks your host instead of the prefilled one. You can save the connection even if the test fails, and the credential is sent only to the hosts in **Allowed websites**.
4042
4143The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See [how Agent Proxy works](/docs/claude-tag/concepts/agent-identity#agent-proxy).
4244
claude-tag/admins/network-requirements Changed · +2 / -0 lines
from line 20
2020
2121The range is shared across Anthropic services, and dedicated per-organization egress addresses aren't available, so the allowlist entry admits Anthropic's infrastructure as a whole. Your credential's [allowed websites](/docs/claude-tag/admins/add-connections#set-allowed-websites) are what scope which of *your* systems Claude can call.
2222
23<Note>If your Google Cloud project uses VPC Service Controls, an IP-based access level doesn't admit Claude's queries through the [BigQuery connection](/docs/claude-tag/admins/connections/bigquery). See [Allow the connection through a VPC Service Controls perimeter](/docs/claude-tag/admins/connections/bigquery#allow-the-connection-through-a-vpc-service-controls-perimeter) on the BigQuery page.</Note>
24
2325Allowlist changes on enterprise systems can take days to take effect, which is why the [prerequisites for setup](/docs/claude-tag/admins/setup-overview) send you here before you start setup.
2426
2527## Internet reachability
claude-tag/admins/setup-overview Changed · +3 / -1 lines
from line 46
4646 **Where:** the Slack Marketplace, at [claude.com/claude-for-slack](https://claude.com/claude-for-slack).
4747
4848 Click **Add the Claude app** on the setup page to open the listing, then click **Add to Slack** and approve the permissions. If the app is already installed, click **Add to Slack** anyway: you reinstall over the existing app with its current permissions and keep your settings.
49
50 On Slack Enterprise Grid, installing takes two Slack actions. See [Set up Claude Tag on Enterprise Grid](/docs/claude-tag/admins/workspaces#set-up-claude-tag-on-enterprise-grid) for the steps.
4951 </Step>
5052
5153 <Step title="Send @Claude connect in any channel">
from line 96
9496</Accordion>
9597
9698<Accordion title="If your Slack is on Enterprise Grid">
97 When a Grid org admin sends `@Claude connect`, the reply includes two codes: a `workspace_` code that pairs only that workspace, and an `enterprise_` code that pairs every workspace in the Grid that doesn't already have its own pairing. Paste the `enterprise_` code if Claude should work across the Grid; DMs for users homed in other Grid workspaces only work with a Grid-wide pairing. See [Pair an Enterprise Grid](/docs/claude-tag/admins/workspaces#pair-an-enterprise-grid).
99 When a Slack Org Owner or Org Admin sends `@Claude connect`, the reply includes two codes. One begins `workspace_` and pairs only the workspace the admin sent the command in, and one begins `enterprise_` and pairs the whole Grid. Paste the `enterprise_` code. See [Pair an Enterprise Grid](/docs/claude-tag/admins/workspaces#pair-an-enterprise-grid).
98100</Accordion>
99101
100102## Choose Claude's first tools
claude-tag/concepts/security-and-data Changed · +3 / -1 lines
from line 89
8989
9090Claude doesn't work in a channel shared with another company through [Slack Connect](/docs/claude-tag/admins/restrict-access#slack-connect-channels), so no access bundle's credentials reach one.
9191
92When you ask Claude in one channel to post into another, Claude works with the access bundles and instructions of the channel you asked in, not the target channel's. From a private channel, Claude doesn't post anywhere else, and nothing asked elsewhere makes Claude post into a private channel. [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels) covers where Claude can post from each place you ask.
93
9294Isolating a credential doesn't isolate what Claude knows. The [workspace notes](/docs/claude-tag/users/memory) it saves from a public channel are read by sessions in every channel of the workspace, and it can [search public channels by keyword](/docs/claude-tag/admins/restrict-access#controls-that-aren%E2%80%99t-available) without being added to them, the same way any workspace member can.
9395
9496## Artifact visibility
9597
96A session can publish an artifact, a web page hosted on claude.ai with the link posted in the thread, and the page stays available after the sandbox is released. Anyone with access to the source Slack channel can open it, which in a public channel covers everyone in the workspace. Someone who opens the link without that access sees a request-access prompt rather than the page. There is no share setting for anyone to change. Updates go through Claude: ask in the Slack thread, or [send Claude a comment on the page](/docs/claude-tag/users/use-cases/create-artifacts#comment-on-the-page-to-ask-for-changes), which anyone who can post in the channel can do.
98A session can publish an artifact, a web page hosted on claude.ai with the link posted in the thread, and the page stays available after the sandbox is released. Anyone with access to the source Slack channel can open it, which in a public channel covers everyone in the workspace. Someone who opens the link without that access can't see the page and has no option to request access. There is no share setting for anyone to change. Updates go through Claude: ask in the Slack thread, or [send Claude a comment on the page](/docs/claude-tag/users/use-cases/create-artifacts#comment-on-the-page-to-ask-for-changes), which anyone who can post in the channel can do.
9799
98100While a Slack guest is in a channel set to [**Channel only**](/docs/claude-tag/admins/restrict-access#how-channel-only-works), Claude doesn't publish artifacts there.
99101
claude-tag/users/when-claude-responds Changed · +1 / -1 lines
from line 38
3838
3939The **Respond automatically** setting controls whether Claude replies to a channel's messages without an @-mention. When it's on, Claude may reply to a message it judges warrants one, as [What Claude does with a channel message](#what-claude-does-with-a-channel-message) describes. When it's off, Claude replies in that channel only when someone @-mentions it.
4040
41The setting is on by default, so a channel Claude was just added to replies without @-mentions from the start.
41The setting is on by default.
4242
4343Each channel has its own copy of the setting, and there is no workspace- or organization-wide version. To make Claude mention-only across many channels, turn it off in each one.
4444