One read of Claude Documentationclaude-docs-20260930T203705Z
3 pages moved out of 258 read.
Pages moved
3
significant first
Pages read
258
in this capture
Captured
20:37 UTC
Corpus hash
f34820e18f83
corpus-hash
What this read moved
1-3 of 3claude-tag/admins/managed-by Changed · +49 / -0 lines
### Correct Claude privately from a managing channel
from line 18
1818| :- | :- | :- |
1919| The same rules in every channel of a workspace or your whole organization | [Custom instructions](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions) on the workspace or organization scope | An Owner, or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) for the workspace scope, in admin settings |
2020| A central team to write the rules for a few channels it runs, such as a help desk or an on-call channel, without being admins | **Managed by** | Members of a managing channel, by asking Claude in Slack |
21| To correct how Claude behaves in a channel without having the conversation in that channel | **Managed by** with a private managing channel, as in [Correct Claude privately from a managing channel](#correct-claude-privately-from-a-managing-channel) | You, by asking Claude in the private channel |
2122| The people who work in a channel to set its conventions themselves | The **Channel instructions** field on the channel's [Configure page](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel) | Channel members, unless an admin has [restricted editing](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) |
2223
2324You set up **Managed by** one channel at a time, and someone confirms each change to a channel's text in Slack. That suits a handful of channels. To give many channels the same text, use workspace or organization custom instructions.
from line 32
3132* **Every channel in the pairing:** Claude is a member, and the channel is an ordinary channel in the same Slack workspace as the others. Direct messages and group direct messages can't be managed or managing channels.
3233* **Sharing:** no channel in the pairing is shared outside its workspace. That rules out Slack Connect channels, including ones with a pending invitation, and channels shared across the workspaces of an Enterprise Grid.
3334* **You:** you are a member of every managing channel you add.
35* **Managing channel:** its [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) setting resolves to **Allow**. The list accepts a managing channel set to **Block**, but Claude refuses every read and change there.
3436* **Managed channel:** the channel has its own channel scope on the **Slack** tab in admin settings. If it doesn't appear there, [add the channel](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel).
3537
3638A managed channel can have up to five managing channels. A private managed channel has extra rules, listed under [Public and private channels](#public-and-private-channels).
from line 93
9193* **Long rewrites:** Claude proposes a long rewrite in parts. After you confirm one part, ask for the next in a new message.
9294* **Text changed since Claude read it:** confirming the card changes nothing. Ask Claude again so it proposes the change against the current text.
9395
96### Correct Claude privately from a managing channel
97
98A managing channel is a Slack channel that an Owner or Admin selected under **Managed by** on another channel's Configure page, and that other channel is the managed channel. When Claude gets something wrong in the managed channel, you can give the correction in a private managing channel, where only the private channel's members see the conversation.
99
100Claude proposes the correction as a change to the managed channel's instructions. After you confirm, Claude follows the new text in [conversations that start afterward](#how-managed-instructions-load) in the managed channel. While a guest is present in a managed channel that runs with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works), Claude doesn't load managed instructions.
101
102<Steps>
103 <Step title="Set up a private managing channel">
104 Skip this step if the managed channel already has a private managing channel that you're in. Otherwise, create a private channel in Slack and run `/invite @Claude` in it. Then an Owner or Admin who is a member of the private channel selects it, following [Choose the managing channels](#choose-the-managing-channels). If you're that Owner or Admin, you and Claude can be the private channel's only members.
105
106 To open the Configure page without posting in the managed channel, select the **Configure** link in the footer of a Claude reply there.
107 </Step>
108
109 <Step title="Ask Claude in the private managing channel">
110 Start a new thread, mention Claude, tell it which thread it got wrong, and say what it should do next time.
111
112 * **Public managed channel:** paste the thread's link. Claude can read the linked thread as long as the managing channel has no guests. If it has guests, describe what happened.
113 * **Private managed channel:** describe what happened, because Claude reads a private channel's threads only from inside that channel
114
115 ```text wrap theme={null}
116 @Claude in this #it-help thread you told someone to email IT about a new laptop: https://example.slack.com/archives/C0123456789/p1700000000000000
117 Add a rule to the instructions for #it-help that laptop requests get a link to the hardware form.
118 ```
119
120 Claude reads any thread you linked and the managed channel's current text, then posts a card in the managing channel that shows every line the change adds or removes.
121 </Step>
122
123 <Step title="Confirm the card">
124 Select **Confirm** if the wording is right. To reword it, select **Cancel** and tell Claude what to change. The card expires 10 minutes after Claude posts it. After you confirm, the card says that the managed channel's instructions were updated.
125 </Step>
126
127 <Step title="Read the text back">
128 In a new message in the managing channel, ask Claude to show the managed channel's instructions. Claude replies there with the current text.
129 </Step>
130</Steps>
131
132People who are in the managed channel and not in the managing channel see only part of a correction.
133
134* **Your messages, Claude's replies, and the card:** these stay in the managing channel. Claude posts nothing in the managed channel when you confirm.
135* **The instruction text:** members of the managed channel can ask Claude to repeat its instructions, so write the correction as a rule you're comfortable with them reading. They can also ask Claude to change or remove the text, as described in [Limits of Managed by as a control](#limits-of-managed-by-as-a-control).
136
137In the original thread, Claude keeps the text the thread started with, and its replies there stay as they are. From a private channel, Claude [doesn't post in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels), so reply in that thread yourself if the person who asked needs the right answer.
138
94139## How managed instructions load
95140
96141Managed instructions are either core instructions, which Claude always reads, or reference files, which Claude opens when the core instructions call for one.
from line 145
100145| Core instructions | One per managed channel | 16 KiB | At the start of every new conversation in the managed channel |
101146| Reference files | Up to 20 per managed channel, each with a short name | 100 KiB each | When the core instructions point Claude to one by name |
102147
148While a guest is present in a managed channel that runs with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works), Claude doesn't read the channel's memory, where managed instructions are stored, so conversations start without them.
149
103150Put what Claude must always follow in the core instructions. Put long material, such as a runbook or an escalation list, in a reference file, and name that file in the core instructions so Claude knows when to open it.
104151
105152Claude reads standing instructions in this order:
from line 194
147194| This channel isn't set as a manager of the other channel | No pairing exists, or it was removed | Add this channel under **Managed by** on the other channel's Configure page |
148195| A channel is shared with another organization | The managed or managing channel is a Slack Connect channel, has a pending invitation, or is shared across Enterprise Grid workspaces | Use channels that belong to one workspace only |
149196| You aren't in the managing channel, or in the private managed channel | You tried to add a managing channel you haven't joined, or to add managing channels to a private channel you aren't in | Join the channel in Slack, then try again |
197| This channel's settings are locked by an admin | The managing channel's [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) setting is **Block**, on the channel or inherited from its workspace or **Default Slack access** | Set **Channel member edits** to **Allow** on the managing channel's scope |
198| You need your Claude account connected in this organization | You selected **Confirm** or **Cancel** without a Claude account in the organization connected to your Slack account | Connect your account from the Claude app's **Home** tab in Slack, then select the button again |
150199| Claude isn't in one of the channels | Claude was removed from the managed or managing channel, or never added | Run `/invite @Claude` in that channel |
151200| One of those channels is archived | One of the managing channels is archived in Slack | Remove the archived channel, then try again |
152201| A private channel can only be managed by private channels | The managed channel is private and the managing channel is public, or was made public later | Pick a private managing channel |
claude-tag/admins/customize Changed · +1 / -0 lines
from line 24
2424| Setting | What it does | More |
2525| :- | :- | :- |
2626| Custom instructions | Standing guidance read in every session on a scope, like team conventions. Outranks channel memory. | [Add custom instructions](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions) |
27| Managed by | Which other Slack channels' members can write a channel's standing instructions by asking Claude, including from a private channel. An Owner or Admin in your Claude organization sets it on the **Admin** tab of the channel's Configure page. | [Manage a channel's instructions from another channel](/docs/claude-tag/admins/managed-by) |
2728| Respond automatically | Whether Claude replies to a channel's messages without an @-mention. **Respond automatically** exists only on channels, not on workspaces or your whole organization. Channel members can change it too, from Slack or the channel's Configure page, unless the scope's [**Channel member edits**](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) setting is **Block**. | [Turn automatic replies on or off](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) |
2829| Plugins | Bundles of skills that teach Claude how to use a specific tool | [Attach plugins](/docs/claude-tag/admins/add-connections#attach-plugins) |
2930| Connections | Which systems it can reach from each channel | [Add connections](/docs/claude-tag/admins/add-connections) |
claude-tag/users/good-habits Changed · +1 / -0 lines
from line 165
165165| How this channel should behave: format, tone, when to respond | [**Channel memory**](/docs/claude-tag/users/memory) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |
166166| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](/docs/claude-tag/admins/configure-github#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |
167167| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) | This channel |
168| A correction for this channel that you don't want to raise in the channel | [**Managed instructions**](/docs/claude-tag/admins/managed-by#correct-claude-privately-from-a-managing-channel), written from a private managing channel | Full workspace members in the managing channel who have a Claude account in your organization, after an Owner or Admin sets it up | This channel |
168169| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](/docs/claude-tag/admins/skills-repo) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every channel under the scope it's attached to |
169170| Standing rules across many channels | [**Custom instructions**](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions) on a workspace or organization scope | An organization Owner, or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) for a workspace scope, in the console | Every session in that scope |
170171