Troubleshoot Claude Tag in channels and DMs changedclaude-tag/users/troubleshooting
Nearest release: v2.1.245, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+12added
Lines−5removed
From line
106
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits32to this page, all time
The whole hunk
from line 106, old and new numbered
/
from line 106
106106
107107**What you see**
108108
109Mentions in a channel shared with another company get no answer. A direct mention gets a short notice that Claude doesn't respond there; anything else gets nothing.
109Mentions in a Slack Connect channel, one shared with another company, get no answer, and usually no notice.
110110
111111**What it means**
112112
113Claude doesn't operate in Slack Connect channels, the ones shared with another company. This holds regardless of admin settings. A direct mention gets the reply "This channel is shared with another organization through Slack Connect, and Claude doesn't respond in Slack Connect channels yet." Other messages there are dropped without a reply. See [externally shared channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
113By default, Claude is off in Slack Connect channels, and it posts no notice there. A Claude organization Owner turns it on with the [guest setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels), after which Claude replies with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works). If the setting is already **Allow** or **Channel only** and Claude still doesn't answer, one of two things is likely:
114
115* The organization that runs Claude restricts it to its own members, and you're on the other side of the channel.
116* That organization installed Claude at the Enterprise Grid organization level, and the other company's workspace created the channel.
117
118See [Slack Connect channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
119
120If the mention gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," the thread started before the channel was shared. Mention `@Claude` in a new thread.
114121
115122A channel shared across workspaces inside your Enterprise Grid isn't silent; what happens there depends on how those workspaces connect to Claude. 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.
116123
No line in this hunk matches that.