Restrict where Claude Tag operates changedclaude-tag/admins/restrict-access
Nearest release: v2.1.302, published an hour 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 16 Oct 2026 18:22 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 16 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−0removed
From line
269
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits50to this page, all time
The whole hunk
from line 269, old and new numbered
/
from line 269
269269* **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.
270270* **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.
271271* **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.
272* **Messages from other apps, bots, and workflows.** Claude doesn't reply to a message another app, bot, or Slack workflow posts in a Slack Connect channel, even one that mentions `@Claude`. Claude still reads the message as context, so a person who replies to it with `@Claude` gets an answer.
272273
273274### Channels shared across workspaces in your Enterprise Grid
274275
No line in this hunk matches that.