Troubleshoot Claude Tag setup changedclaude-tag/admins/troubleshooting
Nearest release: v2.1.284, published 6 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 28 Sep 2026 23:27 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 28 Sep 2026 23:37 UTC.
Upstream edited
Recorded here
Lines+32added
Lines−16removed
From line
211
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits27to this page, all time
### This channel is open to more than one Slack workspace ### This channel is shared across several Slack workspaces
The whole hunk
from line 211, old and new numbered
/
from line 211
211211
212212> This channel is shared across multiple workspaces, and Claude can't verify whether it includes guests, so Claude can't respond here.
213213
214When the reason Claude can't verify the membership is that the channel is shared with a workspace in your Enterprise Grid where the Claude app isn't installed, the reply reads instead:
215
216> This channel is shared with a workspace Claude hasn't been added to, so Claude can't check the channel for guests and can't respond here. A Slack org admin can add Claude to that workspace.
217
214218The same check also refuses requests made from another conversation, such as asking Claude to post a message in the channel, with a message ending "shared across multiple workspaces and Claude can't verify whether it includes guests".
215219
216220**What it means**
from line 223
219223
220224**How to resolve**
221225
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).
226The fix depends on which reply Claude posted:
223227
228* If the reply says the channel is shared with a workspace Claude hasn't been added to, have a Slack org admin [add the Claude app to that workspace](/docs/claude-tag/admins/workspaces#set-up-claude-tag-on-enterprise-grid). Once every workspace sharing the channel has the app, the membership check can run.
229* Otherwise, use a channel that belongs to a single workspace.
230
231Setting 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:
232
233* 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.
234* 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).
235
224236### This channel is shared among several Claude workspaces
225237
226238**What you see**
from line 247
235247
236248The 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.
237249
238Two 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 shared across several Slack workspaces](#this-channel-is-shared-across-several-slack-workspaces) is the case where every workspace belongs to your one Claude organization, so Claude replies.
250Two 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.
239251
240252**How to resolve**
241253
242254Move the conversation to a channel that belongs to a single workspace, or to a DM.
243255
244### This channel is shared across several Slack workspaces
256### This channel is open to more than one Slack workspace
245257
246258**What you see**
247259
248260Claude posts a notice in the thread, then answers the request:
249261
250> This channel is shared across several Slack workspaces, so Claude is using only your organization's default Slack access and settings here — not any workspace- or channel-specific repos, instructions, or memory you've configured.
262> This channel is open to more than one Slack workspace, so Claude uses your organization's default settings here, not workspace- or channel-specific ones. A Claude organization owner can change the defaults in [Claude Tag settings](https://claude.ai/admin-settings/claude-tag).
251263
252264**What it means**
253265
254266The 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.
255267
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.
268Claude posts the notice about once a month in each such channel, not on every reply, so replies there run under the same defaults even when no notice accompanies them.
257269
258270**How to resolve**
259271
from line 412
400412
401413**What you see**
402414
403In one thread, an "is thinking…" line appeared under a request and no reply followed, while Claude kept answering normally in other channels and threads.
415In one thread, a working indicator appeared under a request and no reply followed, while Claude kept answering normally in other channels and threads.
404416
405417**What it means**
406418
407First check the thread for a notice from Claude that begins `:mute: Claude is muted in this thread`. If that notice is there, the thread is muted and the session isn't stuck. A 👎 reaction on one of Claude's replies mutes the thread and posts that notice. If Claude's session for the thread was partway through a reply, the reaction also stops that reply.
419First check the thread for either of two notices from Claude:
408420
421* A notice that begins `:mute: Claude is muted in this thread` means the thread is muted and the session isn't stuck. A 👎 reaction on one of Claude's replies mutes the thread and posts that notice. If Claude's session for the thread was partway through a reply, the reaction also stops that reply.
422* A notice that ends `stopped Claude's response in this thread. Mention @Claude to pick up again.` means someone selected **Stop** on the working indicator. The session is intact, and a mention continues it.
423
409424To 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.
410425
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.
426Without either 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.
412427
413428**How to resolve**
414429
from line 493
478493
479494> This workspace isn't set up for Claude Tag yet. A workspace admin can run `@Claude connect`, or set it up here.
480495
481The reply varies with the sender: someone who isn't a Slack workspace admin is told to ask their Claude workspace owner to run `@Claude connect`, without the settings link.
496The reply varies with the sender: someone who isn't a Slack workspace admin is told to ask their Claude workspace owner to run `@Claude connect`, without the settings link. In a channel shared across workspaces in an Enterprise Grid where none of the sharing workspaces is paired yet, the reply reads "None of the Slack workspaces this channel is shared with is set up for Claude Tag yet. A workspace admin can set one up here."
482497
483498**What it means**
484499
485The Slack workspace hasn't been paired with a Claude organization.
500The Slack workspace hasn't been paired with a Claude organization, or, for the shared-channel form, none of the workspaces sharing the channel has.
486501
487502**How to resolve**
488503
from line 761
746761| "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) |
747762| "Claude is having trouble starting sessions right now. Try again in a minute." | The service that runs sessions is briefly unavailable; retry |
748763| "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 |
764| "Session failed to start: the environment's setup script exited with an error. Fix the setup script in your environment settings, then mention Claude in this thread to retry." | The setup script of the [environment the scope uses](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope) exited with an error; every session in that scope runs the same script at start, so fix the script, then mention Claude in the thread |
749765
750766**What it means**
751767
No line in this hunk matches that.