Security and data handling changedclaude-tag/concepts/security-and-data
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+1added
Lines−1removed
From line
91
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits27to this page, all time
The whole hunk
from line 91, old and new numbered
/
from line 91
91912. Keep the channel private. Access on a public channel [reaches anyone who joins](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel).
92923. Open the channel from the **Channels** tab under **Claude's access** at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) and check its **Claude's access** table. It lists the access that reaches the channel, and an item a bundle brings is listed under that bundle's row. The **Inheritance** column shows whether each bundle, and each item outside a bundle, was added on the channel's page or inherited from the workspace or from **Slack**.
9393
94Connector credentials reach a channel shared with another company through [Slack Connect](/docs/claude-tag/admins/restrict-access#slack-connect-channels) only through a bundle an Owner attaches directly to that channel after it's shared, or one attached specifically for Slack Connect channels. Claude can then use those credentials for anyone it answers there, including the other company's people. No other credential reaches it: not a bundle attached before the channel was shared or by someone who isn't an Owner, not one inherited from the workspace or the **Slack** page, and not members' [personal connectors](/docs/claude-tag/concepts/personal-connectors).
94In a channel shared with another company through [Slack Connect](/docs/claude-tag/admins/restrict-access#slack-connect-channels), once Claude is turned on there, it has the connector credentials from the [bundles attached directly to that channel](/docs/claude-tag/admins/restrict-access#what-access-claude-has-in-a-slack-connect-channel), including bundles attached before the channel was shared. It also has those from any bundle attached specifically for Slack Connect channels, and it can use them for anyone it answers there, including the other company's people. Credentials inherited from the workspace or the **Slack** page don't reach that channel, and neither do members' [personal connectors](/docs/claude-tag/concepts/personal-connectors). Before you share a channel that already has bundles, check its **Claude's access** table and [remove the channel from any bundle](/docs/claude-tag/admins/attach-to-scope#choose-where-a-bundle-applies) you don't want used for the other company's people.
9595
9696When you ask Claude in one channel to post into another, Claude works with the access and instructions of the channel you asked in, not the target channel's. From a private channel, Claude doesn't post anywhere else, and nothing asked elsewhere makes Claude post into a private channel. [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels) covers where Claude can post from each place you ask.
9797
No line in this hunk matches that.