Restrict where Claude Tag operates changedclaude-tag/admins/restrict-access
Nearest release: v2.1.318, published 3 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 4 Nov 2026 01:09 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 4 Nov 2026 01:37 UTC.
Upstream edited
Recorded here
Lines+6added
Lines−0removed
From line
123
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits54to this page, all time
The whole hunk
from line 123, old and new numbered
/
from line 123
123123
124124If someone invites the app into another channel afterward, Claude stays silent there. Mentioning `@Claude` in that channel gets a notice that Claude is disabled in the channel, not a reply. In a Slack Connect channel, Claude posts no notice.
125125
126Claude doesn't join a new channel that matches an [auto-join pattern](#block-or-auto-join-channels-by-name) while the channel's workspace follows the off state on the **Slack** page. To add a channel later, invite Claude to it in Slack and turn on its **Enable Claude Tag in this channel** switch at the top of the **General** tab on the channel's page.
127
126128One-to-one DMs, guest channels, and shared channels sit outside the per-scope switches:
127129
128130* **One-to-one DMs.** The per-scope switches don't cover one-to-one DMs from members who have connected a Claude account. To close those off too, turn off the [**Allow direct messages**](#allow-or-disable-direct-messages) toggle. For members who haven't connected an account, see [Stop direct messages from members without a Claude account](#stop-direct-messages-from-members-without-a-claude-account).
from line 141
139141
140142* **Blocked channel patterns**: Claude won't read or respond in a channel whose name matches, even if someone invites it there. When it's added to such a channel or @-mentioned in one, it posts a notice that an admin has blocked it there, and otherwise stays silent. In a Slack Connect channel, it posts no notice.
141143* **Auto-join channels**: Claude joins a public channel whose name matches one of its patterns when the channel is created or renamed. Private channels still need an invite. To add Claude to an existing channel, invite it as usual.
144
145> [!NOTE]
146>
147> An auto-join pattern doesn't turn Claude on in a channel, and Claude doesn't join a matching channel while the **Enable Claude Tag** switch that covers it is off. A new channel has no setting of its own, so it follows its workspace's setting or, when the workspace has none, the setting on the **Slack** page. To have Claude respond in a matching channel while it's off elsewhere, turn on that channel's own switch as described in [Limit Claude Tag to specific channels](#limit-claude-tag-to-specific-channels).
142148
143149Each row of the **Auto-join channels** table is one pattern, added with **Add pattern**. A row can also carry [bundles](https://claude.com/docs/claude-tag/admins/attach-to-scope.md#attach-a-bundle-to-channels-by-name), which attach in every matching channel Claude is in; a row with no bundles is marked **Auto-join only**, and Claude joins matching channels whether or not a row carries bundles. A channel rule added with **Add a channel rule…** on the **Channels** tab shows up as a row here too. Editing the patterns or the bundles on a row needs an Owner of your Claude organization.
144150
No line in this hunk matches that.