Troubleshoot Claude Tag in channels and DMs changedclaude-tag/users/troubleshooting
Nearest release: v2.1.296, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 9 Oct 2026 19:07 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 9 Oct 2026 19:37 UTC.
Upstream edited
Recorded here
Lines+20added
Lines−14removed
From line
107
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits31to this page, all time
### Claude is silent in a channel shared with another company ### Claude never responds in a channel shared with another company
The whole hunk
from line 107, old and new numbered
/
from line 107
107107
108108Send a new message with the mention included.
109109
110### Claude never responds in a channel shared with another company
110<a id="claude-never-responds-in-a-channel-shared-with-another-company" />
111111
112### Claude is silent in a channel shared with another company
113
112114**What you see**
113115
114A mention in a Slack Connect channel, one shared with another company, gets a notice that Claude isn't turned on for Slack Connect channels, and no answer.
116A mention in a Slack Connect channel, one shared with another company, gets no answer and no notice, gets a reply only you can see, or gets a notice saying the thread's earlier session can't continue.
115117
116118**What it means**
117119
118Claude doesn't work in [Slack Connect channels](/docs/claude-tag/admins/restrict-access#slack-connect-channels), and no admin setting turns it on there. If the channel became a Slack Connect channel after Claude was added, Claude stops answering from then on, including in threads it was already part of.
120Find what you saw in this list:
119121
122* **No answer and no notice.** By default, Claude is off in Slack Connect channels and posts no notice there. An Owner or a Claude Tag admin can [turn Claude on for Slack Connect channels](/docs/claude-tag/admins/restrict-access#slack-connect-channels). If your admin has turned Claude on and it still doesn't answer, your admin can check the cases listed there.
123* **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.
124* **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.
125
120126A 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.
121127
122128Where 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".
123129
124Each of these messages means the channel spans more than one workspace. The [admin entries on these messages](/docs/claude-tag/admins/troubleshooting#this-channel-is-shared-across-multiple-workspaces) explain what causes each one and what an admin can change.
130Each of these Enterprise Grid messages means the channel spans more than one workspace. The [admin entries on these messages](/docs/claude-tag/admins/troubleshooting#this-channel-is-shared-across-multiple-workspaces) explain what causes each one and what an admin can change.
125131
126132**How to resolve**
127133
128Move the conversation to an internal channel that belongs to a single workspace, or to a DM, and mention Claude there.
134Move the conversation to an internal channel that belongs to a single workspace, or to a DM, and mention Claude there. For a Slack Connect channel, you can also ask your admin to [turn Claude on there](/docs/claude-tag/admins/restrict-access#slack-connect-channels).
129135
130136### Couldn't check this channel just now
131137
No line in this hunk matches that.