Configure per-channel access changedclaude-tag/admins/attach-to-scope
Nearest release: v2.1.283, published 5 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 25 Sep 2026 23:59 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 22:07 UTC.
Upstream edited
Recorded here
Lines+19added
Lines−19removed
From line
18
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits29to this page, all time
The whole hunk
from line 18, old and new numbered
/
from line 18
1818
1919<img className="hidden dark:block" src="https://mintcdn.com/claude-ai/5JFKyLlO7sHMMf5J/images/claude-tag/diagrams/scope-inheritance-dark.svg?fit=max&auto=format&n=5JFKyLlO7sHMMf5J&q=85&s=b53a534b076e6c22f0d86a81841b00a8" alt="Nested boxes. The outermost box is the Default Slack access scope: a bundle attached here is the baseline every channel gets. Inside it, two examples. Outside the workspace box, a channel called another-team in a different workspace gets only the default bundle. Inside the workspace box, which adds an optional bundle for channels inside it, two channel boxes: a public channel called general, with no channel bundle, gets the default plus the workspace bundle; a private channel, marked with a lock, with its own channel bundle, gets all three, the default, workspace, and channel bundles." width="1000" height="320" data-path="images/claude-tag/diagrams/scope-inheritance-dark.svg" />
2020
21| Scope | What it covers | Access |
22| :------------------- | :---------------------------------------- | :---------------------------------------------------------------------- |
23| Default Slack access | Every Slack workspace and channel | The baseline set every channel gets |
24| Workspace | All channels in one Slack workspace | Inherits Default Slack access, plus workspace-level bundles |
25| Channel | A single Slack channel, public or private | Inherits Default Slack access and workspace, plus channel-level bundles |
21| Scope | What it covers | Access |
22| :- | :- | :- |
23| Default Slack access | Every Slack workspace and channel | The baseline set every channel gets |
24| Workspace | All channels in one Slack workspace | Inherits Default Slack access, plus workspace-level bundles |
25| Channel | A single Slack channel, public or private | Inherits Default Slack access and workspace, plus channel-level bundles |
2626
2727The same stacking applies in reverse. Detaching a bundle from a channel removes only that channel's additions, and bundles attached at the workspace or Default Slack access still apply there.
2828
from line 84
8484
8585Each connector or repository row in these sections carries an origin line that says which scope or bundle gave the scope that item.
8686
87| Origin line | What it means |
88| :------------------------- | :------------------------------------------------------------------------------------------------------------------ |
87| Origin line | What it means |
88| :- | :- |
8989| **Inherited from** *scope* | The row comes from a wider scope. When an admin-made bundle carries it, the line adds **via** and the bundle's name |
90| **Attached from** *bundle* | The row was added on this scope through that admin-made bundle |
90| **Attached from** *bundle* | The row was added on this scope through that admin-made bundle |
9191
9292Select the scope name to open that scope, or the bundle name to open the bundle.
9393
from line 123
123123
124124The table lists the kinds of standing instruction that can apply in a channel and who writes each.
125125
126| Layer | Who writes it | Where |
127| :------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------- |
128| Custom instructions | Owner for any scope; channel members and [channel managers](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers) for the channel scope, unless members are [restricted](#restrict-who-can-set-channel-instructions) | The scope's panel in admin settings, or the **Configure** link in any reply footer for the channel scope |
129| Managed instructions | Full workspace members in one of the channel's [managing channels](/docs/claude-tag/admins/managed-by), which an Owner or Admin selects under **Managed by** on the channel's Configure page | By asking Claude in the managing channel and confirming the card it posts |
130| Channel memory | Anyone in the channel | By telling Claude to remember |
131| Task prompt | The requester | The message itself |
126| Layer | Who writes it | Where |
127| :- | :- | :- |
128| Custom instructions | Owner for any scope; channel members and [channel managers](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers) for the channel scope, unless members are [restricted](#restrict-who-can-set-channel-instructions) | The scope's panel in admin settings, or the **Configure** link in any reply footer for the channel scope |
129| Managed instructions | Full workspace members in one of the channel's [managing channels](/docs/claude-tag/admins/managed-by), which an Owner or Admin selects under **Managed by** on the channel's Configure page | By asking Claude in the managing channel and confirming the card it posts |
130| Channel memory | Anyone in the channel | By telling Claude to remember |
131| Task prompt | The requester | The message itself |
132132
133133Channel members can shape how Claude responds in their channel through memory, but they can't change which credentials or repositories it has; that's bundle configuration. See [who controls what](/docs/claude-tag/admins/customize) for the full split.
134134
from line 152
152152
153153By default, anyone in a channel who is also a member of your Claude organization can edit that channel's instructions from the **Configure** link in Claude's reply footer. The **Channel member edits** setting in a scope's **Advanced** settings controls this.
154154
155| Option | Effect |
156| :---------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
157| **Inherit** | Follow the parent scope's setting |
158| **Allow** | Members can edit channel instructions from the Configure link |
159| **Block** | Members can't change channel instructions, the channel's default model, or its [**Respond automatically**](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting |
155| Option | Effect |
156| :- | :- |
157| **Inherit** | Follow the parent scope's setting |
158| **Allow** | Members can edit channel instructions from the Configure link |
159| **Block** | Members can't change channel instructions, the channel's default model, or its [**Respond automatically**](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting |
160160
161161A chain of scopes that all inherit resolves to **Allow**. Set **Block** at the workspace or Default Slack access scope to lock channel instructions across every channel beneath it. A [channel manager](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers) can still edit instructions, change the default model, and switch the **Respond automatically** toggle from the Configure page in a channel assigned to them when **Block** is set.
162162
No line in this hunk matches that.