Restrict where Claude Tag operates changedclaude-tag/admins/restrict-access
Nearest release: v2.1.299, published 7 hours after 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 13 Oct 2026 17:06 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 13 Oct 2026 17:07 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−2removed
From line
240
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 240, old and new numbered
/
from line 240
240240
241241When Claude answers in a Slack Connect channel, it follows the channel's own instructions and has:
242242
243* No [bundles](/docs/claude-tag/admins/attach-to-scope) or connections, except a bundle an Owner [attaches directly to the channel](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel) after it's shared with the other company, or one attached specifically for Slack Connect channels. A bundle attached before the channel was shared, or by someone who isn't an Owner, doesn't reach it until an Owner removes it from the channel and attaches it again.
243* No [bundles](/docs/claude-tag/admins/attach-to-scope) or connections inherited from the workspace or the **Slack** page, and none attached by a [channel rule](/docs/claude-tag/admins/attach-to-scope#attach-a-bundle-to-channels-by-name), except a bundle attached specifically for Slack Connect channels. A bundle [attached directly to the channel](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel) still applies, whether it was attached before or after the channel was shared and whoever attached it, unless it's set to apply only in channels with guests. Claude can use the connectors in that bundle for anyone it answers there, including the other company's people.
244244* No instructions set on the workspace or on the **Slack** page.
245245* No memory, skills, or repositories.
246246* No [environment set on the scope](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope). The session runs on the standard environment.
247247
248Treat the channel's instructions as visible to the other company. In a Slack Connect channel, Claude also doesn't search your workspace, look up people or channels, read other channels, publish [artifacts](/docs/claude-tag/concepts/security-and-data#artifact-visibility), or set up [routines](/docs/claude-tag/users/proactivity). Routines set up in the channel before it was shared don't run there.
248Treat the channel's instructions, and the connectors in its bundles, as available to the other company. Before you turn Claude on in a Slack Connect channel, or share a channel where it's already on, check the bundles on the channel's page and [remove the channel from any bundle](/docs/claude-tag/admins/attach-to-scope#choose-where-a-bundle-applies) you don't want used there.
249
250In a Slack Connect channel, Claude also doesn't search your workspace, look up people or channels, read other channels, publish [artifacts](/docs/claude-tag/concepts/security-and-data#artifact-visibility), or set up [routines](/docs/claude-tag/users/proactivity). Routines set up in the channel before it was shared don't run there.
249251
250252#### Who can use Claude in a Slack Connect channel
251253
No line in this hunk matches that.