One read of Claude Documentationclaude-docs-20261104T010709Z
16 pages moved out of 281 read.
Pages moved
16
significant first
Pages read
281
in this capture
Captured
01:07 UTC
Corpus hash
83d22872b3f4
corpus-hash
What this read moved
1-16 of 16claude-tag/admins/migrate-from-earlier Changed · +3 / -3 lines
from line 24
2424
25251. Go to [**Claude's access > Channels**](https://claude.ai/admin-settings/claude-tag?access=channels). A workspace or channel set to Legacy shows **legacy Claude in Slack** in the **Changes from defaults** column.
26262. Open each one, and on its **Advanced** tab set **Claude Tag version** to **New**.
273. The **Slack** row never shows that marker, so also go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack) and set **Claude Tag version** on its **Advanced** tab to **New** if it shows **Legacy**.
273. The **Slack** row never shows that marker, so also go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack) and set **Claude Tag version** on its **Advanced** tab to **New** if it shows **Legacy (disabled)**.
2828
2929**3. Give Claude its connections**
3030
from line 44
4444
4545> [!WARNING]
4646>
47> Since October 5, 2026, the earlier Claude in Slack app, shown as **Legacy** in admin settings, no longer answers in channels of a workspace paired with your Claude organization. A channel there that's still set to Legacy gets a notice that the legacy bot is retired, until you set **Claude Tag version** to **New** on the channel, or on its workspace if the channel inherits the setting. You also can't switch a workspace or channel to Legacy anymore. Direct messages aren't affected. In a workspace that isn't paired, Pro, Max, and Ultra users still get answers from the earlier app in channels, and anyone else with a connected Claude account gets the [workspace setup notice](https://claude.com/docs/claude-tag/admins/troubleshooting.md#this-workspace-isn%E2%80%99t-set-up-for-claude-tag-yet) instead.
47> Since October 5, 2026, the earlier Claude in Slack app, shown as **Legacy (disabled)** in the **Claude Tag version** setting, no longer answers in channels of a workspace paired with your Claude organization. A channel there that's still set to Legacy gets a notice that the legacy bot is retired, until you set **Claude Tag version** to **New** on the channel, or on its workspace if the channel inherits the setting. You also can't switch a workspace or channel to Legacy anymore. Direct messages aren't affected. In a workspace that isn't paired, Pro, Max, and Ultra users still get answers from the earlier app in channels, and anyone else with a connected Claude account gets the [workspace setup notice](https://claude.com/docs/claude-tag/admins/troubleshooting.md#this-workspace-isn%E2%80%99t-set-up-for-claude-tag-yet) instead.
4848
4949## What stays the same
5050
from line 68
6868
6969## Two versions of the same Slack app
7070
71The earlier Claude in Slack and Claude Tag are two versions of the same `@Claude` Slack app, not two apps, so there is nothing to uninstall. You choose which version answers in each workspace and channel with the **Claude Tag version** setting. Set it to **New** or **Inherit**. A workspace or channel can't be switched to **Legacy**, and one that's still on Legacy gets the retirement notice in channels instead of answers. Turning off a workspace's or channel's enable switch silences both versions there.
71The earlier Claude in Slack and Claude Tag are two versions of the same `@Claude` Slack app, not two apps, so there is nothing to uninstall. You choose which version answers in each workspace and channel with the **Claude Tag version** setting. Set it to **New** or **Inherit**. A workspace or channel can't be switched to **Legacy (disabled)**, and one that's still on Legacy gets the retirement notice in channels instead of answers. Turning off a workspace's or channel's enable switch silences both versions there.
7272
7373To tell which version answered in a channel, look at who authored the work. The New version authors code as the Claude GitHub App and keeps work in the channel's thread; if `@Claude` still opens pull requests under the asker's name, that channel is answering with the Legacy version.
7474
claude-tag/admins/restrict-access Changed · +6 / -6 lines
from line 267
267267
268268* **Claude Tag turned off.** The [**Enable Claude Tag** switch](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) that covers the channel is off.
269269* **Blocked name.** The channel's name matches one of the [**Blocked channel patterns**](#block-or-auto-join-channels-by-name).
270* **Legacy version.** The scope's [Claude Tag version](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) is **Legacy**.
270* **Legacy version.** The scope's [Claude Tag version](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) is **Legacy (disabled)**.
271271* **Enterprise Grid organization-level installs.** Claude is installed for your whole Enterprise Grid organization rather than per workspace, and none of your own workspaces hosts the channel.
272272* **Threads from before the channel was shared.** Claude doesn't continue a thread it was already working in before the channel was shared. A mention there gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," and a new thread works.
273273* **Messages from the other company's Claude.** Claude doesn't reply to the other company's Claude. If the other company also uses Claude, each company's settings decide only whether its own Claude answers.
from line 277
277277
278278What 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.
279279
280When 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 [**Slack**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md) page. 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.
280When the workspaces all belong to your one Claude organization and **Respond in all channels** is on, Claude replies in the channel, but only with the access and settings on your organization's [**Slack**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md) page. 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. With **Respond in all channels** off, a mention can get a notice saying Claude is off instead of a reply, even where a workspace's or channel's own enable switch is on.
281281
282282When the workspaces belong to different Claude organizations, each with its own settings and plan, Claude won't reply and posts a refusal message instead.
283283
from line 389
389389
390390## Delegate Claude Tag administration
391391
392On the Enterprise plan, the **Claude Tag Admin** permission lets a member of your Claude organization administer Claude Tag without the Owner role. It's a permission in [custom roles](https://claude.ai/admin-settings/roles), listed under **Product admin** in the role editor; an Owner sets it up. To delegate the setup of one channel instead, add a [channel manager](#delegate-channel-setup-to-channel-managers).
392On the Enterprise plan, the **Claude Tag Admin** permission lets a member of your Claude organization administer Claude Tag without the Owner role. It's a permission in [custom roles](https://claude.ai/admin-settings/roles), listed under **Product controls** in the role editor; an Owner sets it up. To delegate the setup of one channel instead, add a [channel manager](#delegate-channel-setup-to-channel-managers).
393393
394394A member whose custom role includes the permission is a Claude Tag admin. A Claude Tag admin can:
395395
396* Create and edit [bundles](https://claude.com/docs/claude-tag/admins/add-connections.md), including their credentials, domain entries, and repository grants, and attach bundles to the organization, a workspace, or a channel
396* Create and edit [bundles](https://claude.com/docs/claude-tag/admins/add-connections.md), including their credentials, domain entries, repository grants, and [plugins](https://claude.com/docs/claude-tag/admins/add-connections.md#attach-plugins), and attach bundles to the organization, a workspace, or a channel
397397* Edit workspace and channel settings at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), such as custom instructions and the default model
398398* Turn Claude on or off for a workspace or a channel with its **Enable Claude Tag** switch, or for every channel with the **Respond in all channels** switch on the **Slack** page
399399* Add and remove [channel managers](#delegate-channel-setup-to-channel-managers), if the role also sets **Identity & Access** to **Can manage**
from line 415
415415
416416**2. Grant the permission**
417417
418On the role's **Admin permissions** tab, set **Claude Tag Admin**, under **Product admin**, to **Can manage**. Changing the member's role type to **Custom** takes them off the built-in Admin role, so if the member is an Admin today, also set **User Management** to **Can manage** and **Analytics** to **Can view**, both under **Organization admin**. Leave the **Capabilities** and **Connectors** tabs as they are, then select **Save**.
418On the role's **Admin permissions** tab, set **Claude Tag Admin**, under **Product controls**, to **Can manage**. Changing the member's role type to **Custom** takes them off the built-in Admin role, so if the member is an Admin today, also set **User Management** to **Can manage** and **Analytics** to **Can view**, both under **Admin controls**. Leave the **Capabilities** and **Connectors** tabs as they are, then select **Save**.
419419
420420**3. Assign the role through a group**
421421
from line 517
517517| Add a channel manager | Yes | No | No |
518518| Set a channel's default model or repositories from the Configure page | Yes | Yes, in assigned channels | No |
519519| Set a channel's default model by asking Claude in a thread, unless the scope's [Channel member edits](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting is **Block** | Yes | Yes | Yes |
520| Turn a channel's [**Respond automatically**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting on or off | Yes | Yes, in assigned channels | Yes, unless the scope's [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting is **Block** |
520| Change a channel's [**How Claude participates**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting | Yes | Yes, in assigned channels | Yes, unless the scope's [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting is **Block** |
521521| Write channel memory | Yes, in the channel | Yes, in the channel | Yes |
522522| Set channel instructions from the Configure link | Yes | Yes, in assigned channels | Yes, unless the scope's [Channel member edits](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting blocks it |
523523| Create, list, or disable a scheduled job in the channel | Yes, in the channel | Yes, in the channel | Yes |
claude-tag/admins/troubleshooting Changed · +17 / -13 lines
from line 36
3636| A reply from Claude while you're still in setup | A notice that starts "Claude isn't on in this channel yet." | Claude Tag isn't turned on until you finish [Launch Claude Tag](https://claude.com/docs/claude-tag/admins/setup-overview#launch-claude-tag). Finish setup, then mention `@Claude` again. A channel that's turned off after launch gets a different notice; see [Claude is disabled in this channel](#claude-is-disabled-in-this-channel). |
3737| A connected tool to work in your test | “I can't reach…” | Claude isn't told about a connector added after the thread started. Ask it to use the service by name, or start a fresh thread. |
3838| Claude to respond in Slack | "Claude Tag has been turned off for your Claude organization…" | The **Enable Claude Tag in Slack** switch is off. An Owner turns it on at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag). See [the troubleshooting entry](#claude-tag-is-turned-off-for-your-organization). |
39| Claude to respond in Slack | "Claude Tag is unavailable because Routines aren't enabled for your organization…" | Routines isn't enabled for your Claude organization, which Claude Tag requires. An admin turns on [**Admin settings > Capabilities > Remote sessions > Routines**](https://claude.ai/admin-settings/capabilities). Anyone can then mention `@Claude` again. See [the troubleshooting entry](#claude-tag-is-unavailable-because-routines-are-not-enabled). |
39| Claude to respond in Slack | "Claude Tag is unavailable because Routines aren't enabled for your organization…" | Routines isn't enabled for your Claude organization, which Claude Tag requires. An admin turns on [**Organization settings > Capabilities > Remote sessions > Routines**](https://claude.ai/admin-settings/capabilities). Anyone can then mention `@Claude` again. See [the troubleshooting entry](#claude-tag-is-unavailable-because-routines-are-not-enabled). |
4040| Claude to respond in Slack | "Claude in Slack is not available for your organization" or "Claude isn't available for organizations with restricted compliance settings." | The paired Claude organization has a restricted compliance configuration, such as Zero Data Retention (ZDR), that Claude Tag can't run under. No setting lifts the restriction; contact your account team. See [the troubleshooting entry](#restricted-compliance-settings-block-claude-tag). |
4141| The **Slack** page or a workspace or channel page to load | "Couldn't load Slack scopes. Reload the page to try again." | Reload the page. See [Couldn't load Slack scopes](#couldn%E2%80%99t-load-slack-scopes). |
4242| A reply in your test channel | "Couldn't check this channel just now" | Mention `@Claude` again. See [Couldn't check this channel just now](#couldn%E2%80%99t-check-this-channel-just-now). |
from line 228
228228Setting 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:
229229
230230* 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.
231* When they all share your one Claude organization, Claude replies with only your organization's default access and settings, described in [This channel is open to more than one Slack workspace](#this-channel-is-open-to-more-than-one-slack-workspace).
231* When they all share your one Claude organization and **Respond in all channels** is on, Claude replies with only your organization's default access and settings, described in [This channel is open to more than one Slack workspace](#this-channel-is-open-to-more-than-one-slack-workspace).
232232
233233### This channel is shared among several Claude workspaces
234234
from line 244
244244
245245The channel is shared across more than one Slack workspace in your Enterprise Grid, and those workspaces are paired to different Claude organizations. No single organization's settings cover the channel, so Claude declines regardless of the guest policy or any scope setting. Claude also declines when it can't confirm that the workspaces share one Claude organization.
246246
247Two similar messages come from different situations. [This channel is shared across multiple workspaces](#this-channel-is-shared-across-multiple-workspaces) is the guest case, and [This channel is open to more than one Slack workspace](#this-channel-is-open-to-more-than-one-slack-workspace) is the case where every workspace belongs to your one Claude organization, so Claude replies.
247Two similar messages come from different situations. [This channel is shared across multiple workspaces](#this-channel-is-shared-across-multiple-workspaces) is the guest case, and [This channel is open to more than one Slack workspace](#this-channel-is-open-to-more-than-one-slack-workspace) is the notice Claude posts on a reply that uses your organization's default settings.
248248
249249**How to resolve**
250250
from line 496
496496
497497**What it means**
498498
499The workspace is paired with your Claude organization, but the channel's or workspace's **Claude Tag version** is set to **Legacy**. Since that date, the earlier app no longer answers in channels of a paired workspace.
499The workspace is paired with your Claude organization, but the channel's or workspace's **Claude Tag version** is set to **Legacy (disabled)**. Since that date, the earlier app no longer answers in channels of a paired workspace.
500500
501501**How to resolve**
502502
from line 550
550550
551551Claude replies to a mention or a DM:
552552
553> Claude Tag is unavailable because Routines aren't enabled for your organization. Admins can manage Routines at claude.ai → Admin settings → Claude Code.
553> Claude Tag is unavailable because Routines aren't enabled for your organization. Admins can manage Routines at claude.ai → Admin settings → Capabilities → Remote sessions.
554554
555In the message, "claude.ai → Admin settings → Claude Code" is a link to that settings page. When Claude can't check the setting in the moment, the reply reads "Couldn't verify your organization's settings right now. Please try again in a moment." instead.
555When Claude can't check the setting in the moment, the reply reads "Couldn't verify your organization's settings right now. Please try again in a moment." instead.
556556
557557**What it means**
558558
from line 560
560560
561561**How to resolve**
562562
563An admin goes to [**Admin settings > Capabilities > Remote sessions**](https://claude.ai/admin-settings/capabilities) and turns on the **Routines** toggle. Once Routines is enabled for your organization, mention Claude again; a normal reply means the setting took effect. For the "Couldn't verify" reply, wait a moment and mention Claude again.
563An admin goes to [**Organization settings > Capabilities > Remote sessions**](https://claude.ai/admin-settings/capabilities) and turns on the **Routines** toggle. Once Routines is enabled for your organization, mention Claude again; a normal reply means the setting took effect. For the "Couldn't verify" reply, wait a moment and mention Claude again.
564564
565565### Restricted compliance settings block Claude Tag
566566
from line 598
598598
599599Only the first sentence is fixed. A sender who isn't a Slack workspace admin is told to ask their Claude workspace owner to re-enable it, with a link to the Claude Tag product page instead of admin settings.
600600
601In a channel shared across workspaces in your Enterprise Grid, you can instead see a notice that starts "Claude is off in channels shared across your Slack workspaces".
602
601603**What it means**
602604
603This channel's **Enable Claude Tag in this channel** switch is off, either set on the channel's page itself or inherited from its workspace, or from the **Slack** page, whose **Respond in all channels** switch is off. If the **Slack** page has a single [**Respond in channels** switch](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-on-the-team-plan) instead of per-channel switches, the same notice means that switch is off, or the channel's workspace is switched off on its own.
605This channel's **Enable Claude Tag in this channel** switch is off, either set on the channel's page itself or inherited from its workspace, or from the **Slack** page, whose **Respond in all channels** switch is off. If the **Slack** page has a single [**Respond in channels** switch](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-on-the-team-plan) instead of per-channel switches, "Claude is disabled in this channel" means that switch is off, or the channel's workspace is switched off on its own. The notice about channels shared across your Slack workspaces means **Respond in all channels** is off.
604606
605607**How to resolve**
606608
from line 612
6106122. Under **Claude's access**, open the **Channels** tab and select the channel.
6116133. On the **General** tab, turn on the **Enable Claude Tag in this channel** switch.
612614
615For the notice about channels shared across your Slack workspaces, select the **Slack** row in step 2 and turn on **Respond in all channels** in step 3. Turning on a channel's own switch won't clear that notice.
616
613617If the switch is inherited from the **Slack** page, you can instead select the **Slack** row on the **Channels** tab and turn on **Respond in all channels** at the top of its **General** tab. That also turns Claude back on in every other channel that inherits the switch from the **Slack** page.
614618
615619If the **Slack** page has a single [**Respond in channels** switch](https://claude.com/docs/claude-tag/admins/workspaces.md#turn-claude-tag-on-or-off-on-the-team-plan) instead of per-channel switches, select the **Slack** row on the **Channels** tab and check that **Respond in channels** is on. If the fix worked, a mention in the channel gets a reply.
from line 620
616620
617621## Access and connections
618622
619Access and connection errors usually mean Claude responded but couldn't reach a connected service, a repository, or a capability the sender's seat doesn't include. A channel still set to **Legacy** replies with the [retirement notice](#the-legacy-claude-in-slack-bot-is-retired-effective-october-5-2026) rather than an access error.
623Access and connection errors usually mean Claude responded but couldn't reach a connected service, a repository, or a capability the sender's seat doesn't include. A channel still set to **Legacy (disabled)** replies with the [retirement notice](#the-legacy-claude-in-slack-bot-is-retired-effective-october-5-2026) rather than an access error.
620624
621625### Claude says a host isn't allowed or it can't reach the internet
622626
from line 804
800804
801805**What it means**
802806
803Sessions run on the environment or runner pool set on the nearest scope above them, or on the organization's default environment when none is set; [Configure the environment for a scope](https://claude.com/docs/claude-tag/admins/customize.md#configure-the-environment-for-a-scope) covers the picker. The picker only lists environments scoped to the organization; an environment created under an individual account doesn't appear, because channel sessions run with no user account attached.
807Sessions run on the environment or runner pool set on the nearest scope above them, or on the organization's default environment when none is set; [Configure the environment for a scope](https://claude.com/docs/claude-tag/admins/customize.md#configure-the-environment-for-a-scope) covers the picker. The picker only lists environments scoped to the organization.
804808
805809**How to resolve**
806810
claude-tag/concepts/how-it-works Changed · +3 / -3 lines
from line 101
101101| | Claude Tag | Cowork | Claude Code |
102102| :- | :- | :- | :- |
103103| Where | Slack channels | claude.ai chat | Your terminal or IDE |
104| Whose access | The team's: service-account credentials an admin sets per channel | Yours: your personal OAuth connectors | Yours: your local credentials and filesystem |
104| Whose access | The team's: service-account credentials an admin sets per channel, plus your [personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) for your own tasks, with your approval | Yours: your personal OAuth connectors | Yours: your local credentials and filesystem |
105105| Who sees the work | Everyone in the channel | Just you | Just you |
106106| Best for | Shared work the team should see and steer | Personal research and drafting | Hands-on coding in your own checkout |
107107
108The short version: **team work → Claude Tag; personal work → Cowork or Claude Code.** Claude Tag's connections authenticate the agent itself with service accounts, not any person. Personal connectors apply in a one-to-one Claude Tag DM, which runs on your own claude.ai account, the same way Cowork does.
108Claude Tag connectors authenticate the agent itself with service accounts, not any person. Personal connectors apply in a one-to-one Claude Tag DM, which runs on your own claude.ai account. Claude can also [use them in a channel](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) for your own tasks, after you allow it.
109109
110110## Key concepts
111111
112112Three ideas recur across this page and the rest of these docs.
113113
114* **Agent identity**: in channels, Claude acts under its own service accounts that an admin provisions, not as the person who asked. What it can reach is set per channel, so everyone in a channel works with the same access. See [How agent identity works](https://claude.com/docs/claude-tag/concepts/agent-identity.md).
114* **Agent identity**: in channels, Claude acts under its own service accounts that an admin provisions, not as the person who asked. What it can reach is set per channel, so everyone in a channel works with the same access. Claude can also [use your personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors.md) there for your own tasks, after you allow it. See [How agent identity works](https://claude.com/docs/claude-tag/concepts/agent-identity.md).
115115* **Scheduling and long-running work**: a task can run on a schedule, follow a pull request and act when it changes, or keep going across many turns in one thread. The same channel access applies whether a person or a schedule started it. See [Set up routines](https://claude.com/docs/claude-tag/users/proactivity.md).
116116* **Memory**: Claude keeps notes for each channel, and the workspace notes it saves from public channels are read in every channel in the workspace. See [What Claude remembers](https://claude.com/docs/claude-tag/users/memory.md).
117117
claude-tag/users/troubleshooting Changed · +3 / -2 lines
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**: Claude replies in one of these ways, and each needs your admin:
3232 * **A notice that starts "Claude isn't on in this channel yet"**: your admin hasn't finished setting up Claude Tag. Send them [Launch Claude Tag](https://claude.com/docs/claude-tag/admins/setup-overview#launch-claude-tag).
33 * **A notice that starts "Claude is off in channels shared across your Slack workspaces"**: Send them [Claude is disabled in this channel](https://claude.com/docs/claude-tag/admins/troubleshooting.md#claude-is-disabled-in-this-channel).
3334 * **A notice that says "Claude is disabled in this channel"**: Claude Tag is turned off for the channel, its workspace, or the organization. Send them [Claude is disabled in this channel](https://claude.com/docs/claude-tag/admins/troubleshooting.md#claude-is-disabled-in-this-channel).
34 * **A notice that the legacy Claude in Slack bot is retired**: the channel is still set to **Legacy**. Send them [The legacy Claude in Slack bot is retired](https://claude.com/docs/claude-tag/admins/troubleshooting.md#the-legacy-claude-in-slack-bot-is-retired-effective-october-5-2026).
35 * **A notice that the legacy Claude in Slack bot is retired**: the channel still uses the **Legacy (disabled)** version. Send them [The legacy Claude in Slack bot is retired](https://claude.com/docs/claude-tag/admins/troubleshooting.md#the-legacy-claude-in-slack-bot-is-retired-effective-october-5-2026).
3536
3637If `@Claude` still gets no reaction and no reply after all three, send the [admin entries for a silent workspace](https://claude.com/docs/claude-tag/admins/troubleshooting.md#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.
3738
from line 124
123124* **A reply only you can see.** If Claude's reply starts "This is a shared Slack Connect channel, and here I only act on requests from people in the host organization with a connected Claude account", the company that set up Claude in this channel has limited it to its own members.
124125* **A notice about the thread's earlier session.** The notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here" means Claude was working in this thread before the channel was shared. Mention `@Claude` in a new thread.
125126
126A channel shared across workspaces inside your Enterprise Grid is different. When every workspace in the channel belongs to your one Claude organization, Claude answers, but with only your organization's default access and settings, so a repository or an instruction set up for that channel doesn't apply. A notice in the thread points this out from time to time. When the workspaces are connected to different Claude organizations, you see "This channel is shared among several Claude workspaces, so Claude cannot respond here" instead of an answer.
127A channel shared across workspaces inside your Enterprise Grid is different. When every workspace in the channel belongs to your one Claude organization and an admin hasn't turned Claude off for these channels, Claude answers, but with only your organization's default access and settings, so a repository or an instruction set up for that channel doesn't apply. A notice in the thread points this out from time to time. If an admin has turned it off, you can see "Claude is off in channels shared across your Slack workspaces" instead of an answer. When the workspaces are connected to different Claude organizations, you see "This channel is shared among several Claude workspaces, so Claude cannot respond here" instead of an answer.
127128
128129Where guest access is restricted, you may first see "This channel is shared across multiple workspaces, and Claude can't verify whether it includes guests, so Claude can't respond here." If you ask Claude from another conversation to act in one of these channels, such as posting a message there, you see a reply that ends "Claude isn't available in channels shared across your Enterprise Grid".
129130
claude-tag/users/when-claude-responds Changed · +4 / -5 lines
from line 32
3232
3333* **Nothing.** This is the usual outcome, especially in a channel where nobody has told Claude which kinds of messages to answer.
3434* **An offer to help.** When a thread leaves a concrete next step Claude could take for someone, Claude may offer in that thread to take it. The offer is either a one-line reply everyone can see or a [private suggestion](#private-suggestions-from-claude) only that person can see.
35* **A short reply in a thread under the message.** Claude replies on its own only when it already has the answer, from the channel's history or its memory, and the answer fits in one message. Replies of this kind carry the plain name **Claude**; see [The name on a reply](#the-name-on-a-reply).
35* **A short reply in a thread under the message.** Claude may reply on its own when it already has the answer, from the channel's history or its memory, and the answer fits in one message. Replies of this kind carry the plain name **Claude**; see [The name on a reply](#the-name-on-a-reply).
3636* **A working session in the message's thread.** When a message needs investigation, tools, or a longer exchange, Claude starts a working session there and posts the work in that thread. For an untagged message, Claude does this only when someone in the channel has told it to pick up that kind of work, as described below the list.
3737* **A hand-off to work already in progress.** When a message adds to something Claude is already working on in another thread, for example a new detail about a bug it's investigating, Claude passes the message to that working session instead of replying. Claude posts nothing in the channel when it does this; anything the new information changes, it reports in the thread where the work is happening.
3838
from line 85
8585A bot's `@Claude` at the channel's top level gets a reply in a thread under that message, unless any of these is true:
8686
8787* The channel's [**Respond automatically**](#turn-automatic-replies-on-or-off) setting is off.
88* Claude has [stopped reading the channel](#when-claude-stops-reading-a-channel) because of message volume.
8988* The channel is a [Slack Connect channel](https://claude.com/docs/claude-tag/admins/restrict-access.md#when-claude-does-not-answer-in-a-slack-connect-channel), shared with another company. Claude reads what apps, bots, and workflows post there as context but doesn't reply to them.
9089
9190A person's mention reaches Claude in each of these cases.
from line 148
149148* **Message volume.** Claude counts the messages posted in the channel since it last posted there itself, and stops reading when the count gets high enough.
150149* **Inactivity.** When more than 10 days pass without anyone @-mentioning Claude in the channel and without Claude posting there, Claude stops reading.
151150
152While Claude isn't reading a channel, it doesn't reply there unprompted. Claude posts no notice when it stops.
151Claude posts no notice when it stops.
153152
154To start Claude reading again, mention `@Claude` in the channel. A mention from a person reaches Claude in both situations, and once Claude posts its reply, it reads the channel's messages again. A mention inside another app's or bot's message starts Claude reading again only after an inactivity stop.
153To start Claude reading again, mention `@Claude` in the channel. A mention from a person reaches Claude in both situations, and once Claude posts its reply, it reads the channel's messages again. A mention inside another app's or bot's message works the same way, except in the [cases that block a bot's reply](#messages-from-other-apps-and-bots).
155154
156155If unprompted replies don't come back after Claude answers a mention, check **How Claude participates** on the channel's [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). Answering a mention doesn't change the setting, so if the page shows **Only when @-mentioned**, change it to **Respond automatically** in one of the three places listed in [Turn automatic replies on or off](#turn-automatic-replies-on-or-off).
157156
from line 163
164163* **Channels shared across workspaces connected to different Claude organizations.** Every workspace where Claude runs is connected to a Claude organization, the account a company sets up for Claude. When a channel is shared across workspaces connected to different Claude organizations, Claude won't reply there and posts a refusal message instead. You can't tell from Slack how a workspace is connected; the refusal message itself is the signal. Use a channel that belongs to one workspace, or send Claude a DM.
165164* **Slack Connect channels.** By default, Claude is off in [channels shared with another company](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels), and a mention there gets no reply and no notice. An Owner or a Claude Tag admin can turn it on for a channel, a workspace, or all of Slack. Ask whoever runs your Claude plan to change [**How should Claude work in channels with guests**](https://claude.com/docs/claude-tag/admins/restrict-access.md#slack-connect-channels).
166165
167When the workspaces sharing a channel all belong to one Claude organization, Claude replies there, but with only your organization's default access and settings. The repositories, instructions, and memory set up for that channel or its workspaces don't apply, and Claude posts a notice in the thread explaining this from time to time. The guest check above still applies first where guest access is restricted.
166When the workspaces sharing a channel all belong to one Claude organization and an admin hasn't turned Claude off for these channels, Claude replies there, but with only your organization's default access and settings. The repositories, instructions, and memory set up for that channel or its workspaces don't apply, and Claude posts a notice in the thread explaining this from time to time. The guest check above still applies first where guest access is restricted.
168167
169168To confirm a channel's setting, check **How Claude participates** on its [Configure page](https://claude.com/docs/claude-tag/users/good-habits.md#configure-claude-for-a-channel). To confirm an instruction Claude saved, ask `@Claude what do you remember about responding in this channel?`, and see [What Claude Tag remembers](https://claude.com/docs/claude-tag/users/memory.md) for where instructions are stored and how to change them.
170169
claude-tag/admins/add-connections Changed · +1 / -1 lines
from line 134
134134
135135> [!NOTE]
136136>
137> Setup links work for the Bearer and Basic credential types. For other types the button is unavailable.
137> Setup links work for the Bearer and Basic credential types and can't carry path prefixes. For other types, or when the credential has path prefixes, the button is unavailable. To limit a credential a teammate submits through a setup link to specific paths, [restrict it by path](#restrict-by-path-or-method) after you approve it.
138138
139139After the teammate submits the credential, it waits for your approval. Go to [**Notifications**](https://claude.ai/admin-settings/notifications) in admin settings, open the **Requests** tab, and click **Review** on the **Approval needed** row. Then click **Approve** or **Reject**. The credential becomes active only after you approve it.
140140
claude-tag/admins/attach-to-scope Changed · +1 / -1 lines
from line 191
191191| :- | :- |
192192| **Inherit** | Follow the parent scope's setting |
193193| **Allow** | Members can edit channel instructions from the Configure link |
194| **Block** | Members can't change channel instructions, the channel's default model, or its [**Respond automatically**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting |
194| **Block** | Members can't change channel instructions, the channel's default model, or its [**How Claude participates**](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) setting |
195195
196196A chain of scopes that all inherit resolves to **Allow**. Set **Block** on a workspace's page or on the **Slack** page to lock channel instructions across every channel beneath it. A [channel manager](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-channel-setup-to-channel-managers) can still edit instructions, change the default model, and change **How Claude participates** from the Configure page in a channel assigned to them when **Block** is set.
197197
claude-tag/admins/configure-github Changed · +1 / -0 lines
from line 34
3434
3535An organization can also be missing from the table because single sign-on (SSO) on GitHub hides it. A note under the table counts the organizations hidden that way. To make them appear, authorize the Claude app for those organizations on GitHub.
3636
37* An **Enable GitHub integration** button under the table means the GitHub connector is off for your Claude organization, so no accounts to link are listed; click it to turn the connector on
3738* A disabled **Link** button means you can't link that account yet; the button's tooltip names the reason, such as not being an owner of that GitHub organization
3839* A **Needs permissions** status means the installation has a pending request; **Review permissions** takes you to github.com to approve it
3940* An **Authorize SSO** button in place of **Link** means your GitHub token isn't authorized for that organization's SSO; the button opens github.com to authorize it, and you link after returning
claude-tag/admins/customize Changed · +2 / -2 lines
from line 25
2525| :- | :- | :- |
2626| Custom instructions | Standing guidance read in every session on a scope, like team conventions. Outranks channel memory. | [Add custom instructions](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#add-custom-instructions) |
2727| Managed by | Which other Slack channels' members can write a channel's standing instructions by asking Claude, including from a private channel. On the Enterprise plan, an Owner or a [Claude Tag admin](https://claude.com/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) sets it on the **Admin** tab of the channel's Configure page. | [Manage a channel's instructions from another channel](https://claude.com/docs/claude-tag/admins/managed-by.md) |
28| Respond automatically | Whether Claude replies to a channel's messages without an @-mention. **Respond automatically** exists only on channels, not on workspaces or your whole organization. Channel members can change it too, from Slack or the channel's Configure page, unless the scope's [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting is **Block**. | [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) |
28| How Claude participates | When Claude replies to a channel's messages. **How Claude participates** exists only on channels. Channel members can change it too, from Slack or the channel's Configure page, unless the scope's [**Channel member edits**](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#restrict-who-can-set-channel-instructions) setting is **Block**. | [Turn automatic replies on or off](https://claude.com/docs/claude-tag/users/when-claude-responds.md#turn-automatic-replies-on-or-off) |
2929| Plugins | Bundles of skills that teach Claude how to use a specific tool | [Attach plugins](https://claude.com/docs/claude-tag/admins/add-connections.md#attach-plugins) |
3030| Connectors | Which systems Claude can reach from each channel | [Add a connector](https://claude.com/docs/claude-tag/admins/add-connections.md) |
3131| Model | Which Claude model handles sessions in a scope | [Choose the model for a scope](#choose-the-model-for-a-scope) |
from line 92
9292
9393[Fast mode](https://claude.com/docs/claude-tag/users/models.md#run-a-thread-in-fast-mode) gives a thread faster output at a higher cost per token. Claude in Slack and Claude Code share one fast mode setting, so turning it on allows fast mode in both. The setting is off by default on the Team and Enterprise plans.
9494
95To allow fast mode, an Owner goes to [**Admin settings > Claude Code**](https://claude.ai/admin-settings/claude-code) and turns on the **Fast mode** toggle under **Capabilities**. Fast mode draws from usage credits, so also turn those on at [**Admin settings > Usage**](https://claude.ai/admin-settings/usage). For an organization billed through AWS Marketplace, the toggle is locked.
95To allow fast mode, an Owner goes to [**Organization settings > Claude Code**](https://claude.ai/admin-settings/claude-code) and turns on the **Fast mode** toggle under **Capabilities**. Fast mode draws from usage credits, so also turn those on at [**Organization settings > Usage**](https://claude.ai/admin-settings/usage). For an organization billed through AWS Marketplace, the toggle is locked.
9696
9797Turning the toggle on has these effects in Slack:
9898
claude-tag/admins/setup-overview Changed · +2 / -1 lines
from line 25
2525> | :- | :- | :- |
2626> | A **Team or Enterprise plan** on claude.ai | Claude Tag is available on Team and Enterprise plans, on Anthropic's first-party service. It isn't available on individual plans (Free, Pro, Max, or Ultra), or for third-party deployments. | Start a Team or Enterprise plan at [claude.com/pricing](https://claude.com/pricing) |
2727> | A Claude organization **without Zero Data Retention (ZDR), customer-managed encryption (CMEK), or the HIPAA configuration for Claude Code (local mode) and Cowork (local mode)** | Claude Tag stores channel memory and session transcripts, which ZDR doesn't permit. A CMEK policy and the HIPAA configuration don't allow Claude Tag either. | Claude Tag isn't available to organizations with any of these. See [Healthcare organizations](https://claude.com/docs/claude-tag/admins/healthcare.md#plan-and-organization-requirements) |
28> | **Routines** enabled for your Claude organization | Until it is, Claude answers every mention and DM with a reply that it's unavailable and does no work. | An admin turns on [**Admin settings > Capabilities > Remote sessions > Routines**](https://claude.ai/admin-settings/capabilities) |
28> | **Routines** enabled for your Claude organization | Until it is, Claude answers every mention and DM with a reply that it's unavailable and does no work. | An admin turns on [**Organization settings > Capabilities > Remote sessions > Routines**](https://claude.ai/admin-settings/capabilities) |
2929> | **Owner** role in the Claude organization you're setting up | Setup pairs a workspace and turns Claude Tag on, and only an Owner can do either. Roles are per organization, so being an Owner elsewhere doesn't carry over. | Ask an Owner to run setup, or have one promote you at [`claude.ai/admin-settings/members`](https://claude.ai/admin-settings/members) |
3030> | A **Slack workspace admin** | Running `@Claude connect` requires a Slack workspace admin; installing the app usually does too. | If that's someone else, [send them the install request](#if-you-re-not-the-slack-workspace-admin) early (app approval can take time), and plan to be online together when you pair; pairing codes expire 15 minutes after they're issued |
3131> | **Usage credits** (Team plans) | Channel work draws from your organization's usage balance; on a Team plan nothing runs until credits are loaded. | Buy credits at [`claude.ai/admin-settings/usage`](https://claude.ai/admin-settings/usage) |
from line 281
281281* [Glossary](https://claude.com/docs/claude-tag/concepts/glossary.md): bundle, scope, session, and the other terms on this page
282282* [Network requirements](https://claude.com/docs/claude-tag/admins/network-requirements.md): what your services must allowlist so Claude can reach them
283283* [Claude Tag in production at Anthropic](https://claude.com/blog/ai-ci-cd-on-call): how Anthropic runs Claude Tag as its first responder for CI/CD failures
284* [Claude Tag admin guide on Claude Academy](https://academy.claude.com/tutorials/claude-tag-admin-guide): a tutorial that covers what comes after launch, including access, spend, and a phased rollout
284285
claude-tag/admins/workspaces Changed · +2 / -2 lines
from line 90
9090| Label | Effect |
9191| :- | :- |
9292| **New** | Claude Tag. Bundles, skills, and custom instructions apply |
93| **Legacy** | The earlier per-user Claude in Slack. In channels it replies only with a retirement notice, and you can't switch a scope to it; see [Migrate from the earlier app](https://claude.com/docs/claude-tag/admins/migrate-from-earlier.md) |
93| **Legacy (disabled)** | The earlier per-user Claude in Slack. In channels it replies only with a retirement notice. The option is listed only on a scope that's still set to it on its own page; see [Migrate from the earlier app](https://claude.com/docs/claude-tag/admins/migrate-from-earlier.md) |
9494| **Inherit** | Use the parent's value. Not shown on the **Slack** page |
9595
9696Turning off **Respond in all channels** doesn't stop Claude in a workspace or channel whose own enable switch is on. On the Enterprise plan, launching setup for a single workspace turns on that workspace's enable switch, so Claude keeps responding in that workspace. The switch is at the top of the **General** tab on the **Slack** page, which sets the default for every workspace and channel. Direct messages from members who have connected a Claude account are unaffected.
from line 117
117117
118118On the Enterprise plan, and in a Team organization whose Slack configuration can't be expressed as one on-or-off choice, the **Slack** page shows **Respond in all channels** instead, and each workspace and channel page has its own enable switch and **Claude Tag version** setting. A Team organization gets those controls when any of these is true:
119119
120* The **Slack** page, a workspace, or a channel is set to **Legacy**
120* The **Slack** page, a workspace, or a channel is set to **Legacy (disabled)**
121121* A workspace or channel is set to **New** on its own page
122122* A channel is switched off on its own page
123123* A bundle or connector is added directly to a channel
claude-tag/concepts/agent-identity Changed · +2 / -2 lines
from line 50
5050
5151### Agent Proxy
5252
53For each outbound request from the sandbox, other than a GitHub API request or a git operation, Agent Proxy checks the destination against three allow layers. A request goes through if any one of them allows it; a host that none of them allows is blocked.
53For each outbound request from the sandbox, other than a GitHub API request or a git operation, Agent Proxy checks the destination against three allow layers. A request goes through if any one of them allows it, and a host that none of them allows is blocked. When a domain entry that applies to the channel names the host, the environment's network access setting alone doesn't let through an HTTP method that entry doesn't allow.
5454
5555| When the destination | Result |
5656| :- | :- |
5757| Matches a credential's rule, its [allowed websites](https://claude.com/docs/claude-tag/admins/add-connections.md#set-allowed-websites) | The proxy attaches that credential and forwards the request. The credential stays at the proxy; the model and sandbox are not given it. |
58| Is an [allowed domain](https://claude.com/docs/claude-tag/admins/add-connections.md#allow-a-host-without-a-credential) that applies to the channel, but matches no credential | The proxy forwards the request without a credential. |
58| Is an [allowed domain](https://claude.com/docs/claude-tag/admins/add-connections.md#allow-a-host-without-a-credential) that applies to the channel, requested with an HTTP method its domain entry allows, but matches no credential | The proxy forwards the request without a credential. |
5959| Is allowed by the network access setting of the [environment](https://claude.com/docs/claude-tag/concepts/glossary.md#environment) the [scope](https://claude.com/docs/claude-tag/concepts/glossary.md#scope)'s sessions run on | The proxy forwards the request without a credential. |
6060| Matches none of these | The proxy blocks the request. |
6161
claude-tag/concepts/glossary Changed · +1 / -1 lines
from line 51
5151
5252## Environment
5353
54The sandboxed compute configuration a session runs in, including its network access setting. Environments used here must be scoped to the organization, not to an individual account, because channel sessions run with no user account attached.
54The sandboxed compute configuration a session runs in, including its network access setting. Environments you set for channels must be scoped to the organization, not to an individual account.
5555
5656## Personal connector
5757
claude-tag/concepts/personal-connectors Changed · +1 / -1 lines
from line 27
2727* **You ask in a [group DM](https://claude.com/docs/claude-tag/users/group-dms.md).** Claude uses your connectors after you allow it, and only your own requests use them.
2828* **You ask in a one-to-one direct message (DM).** Your connectors apply on their own, because a DM runs on [your own claude.ai account](https://claude.com/docs/claude-tag/concepts/agent-identity.md#direct-message-channels).
2929
30To add or remove connectors on your account, open the **Customize > Connectors** page on claude.ai; see [connectors on claude.ai](https://claude.com/docs/connectors/getting-started.md) for setup.
30To add or remove connectors on your account, open the **Customize > Connectors** page on claude.ai; see [connectors on claude.ai](https://claude.com/docs/connectors/getting-started.md) for setup. To find a connector for a service you use, see [Connectors directory](https://claude.com/docs/connectors/directory.md).
3131
3232### Example calendar request in a channel
3333
claude-tag/users/proactivity Changed · +2 / -2 lines
from line 94
9494
9595## Where a routine posts its results
9696
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](https://claude.com/docs/claude-tag/concepts/how-it-works.md#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`](https://claude.com/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.
97A routine you set up from inside a thread usually reports back in that thread each time it runs. To keep the results in the thread, ask Claude to report back there when you set the routine up.
9898
99If the thread's session [gets stuck](https://claude.com/docs/claude-tag/users/troubleshooting.md#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.
99If a routine's results start posting at the channel's top level instead, disable the routine and set it up again from the thread where you want them.
100100
101101For 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.
102102