One read of Claude Documentationclaude-docs-20261001T230709Z
7 pages moved out of 259 read.
Pages moved
7
significant first
Pages read
259
in this capture
Captured
23:07 UTC
Corpus hash
5d61d6a01194
corpus-hash
What this read moved
1-7 of 7claude-science/connectors-and-skills Changed · +6 / -0 lines
### Update skills imported from GitHub
from line 64
6464
6565Your admin can also add skills for everyone in your organization from claude.ai. See [Organization skills](/docs/claude-science/admin-controls#organization-skills).
6666
67### Update skills imported from GitHub
68
69Skills you import from GitHub don't update automatically, and Claude Science doesn't check for changes on its own. To check, go to **Settings > Skills**, scroll to **Imported**, open the three-dot menu next to the repository's name, and select **Check for updates…**. Claude Science checks the latest commit on the repository's default branch, then lists the skills that may have changed since you imported them, along with any new skills. Changed and new skills are selected by default, so clear the checkbox next to any you don't want before you select the **Update** button.
70
71On Team and Enterprise plans, you can update imported skills only if your organization allows custom skills (see [Custom skills](/docs/claude-science/admin-controls#custom-skills)).
72
claude-tag/admins/managed-by Changed · +8 / -8 lines
from line 8
88
99**Managed by** is a channel setting that names other Slack channels whose members can write that channel's standing instructions for Claude. The channel that carries the setting is the managed channel, and each channel it names is a managing channel. People in a managing channel ask Claude to set or update the managed channel's instructions and confirm the change on a card, and Claude follows that text in every new conversation in the managed channel. This page is for admins who set up the pairing and for the people in a managing channel who write the instructions.
1010
11Setting up **Managed by** takes an Owner or Admin in your Claude organization, the roles that see the **Admin** tab on a channel's Configure page. A managing channel isn't a [channel manager](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers). A channel manager is a person with a role that lets them configure one channel. A managing channel is a Slack channel, and the full workspace members in it can propose and confirm changes.
11Setting up **Managed by** takes an Owner of your Claude organization or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration), the roles that see the **Admin** tab on a channel's Configure page. A managing channel isn't a [channel manager](/docs/claude-tag/admins/restrict-access#delegate-channel-setup-to-channel-managers). A channel manager is a person with a role that lets them configure one channel. A managing channel is a Slack channel, and the full workspace members in it can propose and confirm changes.
1212
1313## When to use Managed by
1414
from line 57
5757
5858## Write or update managed instructions
5959
60A managing channel is a Slack channel that an admin selected under **Managed by** on another channel's Configure page. Any full member of the workspace who is in a managing channel can ask Claude there to change the managed channel's instructions. Guests and people from other organizations can't.
60A managing channel is a Slack channel that an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) selected under **Managed by** on another channel's Configure page. Any full member of the workspace who is in a managing channel can ask Claude there to change the managed channel's instructions. Guests and people from other organizations can't.
6161
6262<Steps>
6363 <Step title="Ask Claude in the managing channel">
from line 95
9595
9696### Correct Claude privately from a managing channel
9797
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.
98A managing channel is a Slack channel that an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) 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.
9999
100100Claude 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.
101101
102102<Steps>
103103 <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.
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 a Claude Tag admin who is a member of the private channel selects it, following [Choose the managing channels](#choose-the-managing-channels). If you're that person, you and Claude can be the private channel's only members.
105105
106106 To open the Configure page without posting in the managed channel, select the **Configure** link in the footer of a Claude reply there.
107107 </Step>
from line 170
170170
171171| Managed channel | Managing channels can be | Who can add managing channels |
172172| :- | :- | :- |
173| Public | Public or private | An Owner or Admin |
174| Private | Private only | An Owner or Admin who is also a member of the private channel |
173| Public | Public or private | An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) |
174| Private | Private only | An Owner or a Claude Tag admin who is also a member of the private channel |
175175
176176Anyone in the workspace can join a public managing channel and confirm changes there, so prefer a private managing channel for anything sensitive.
177177
178When a public managed channel is made private, its managing channels are removed. An Owner or Admin who is a member of the now-private channel can add private managing channels again.
178When a public managed channel is made private, its managing channels are removed. An Owner or a Claude Tag admin who is a member of the now-private channel can add private managing channels again.
179179
180180## Limits of Managed by as a control
181181
from line 199
199199| 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 |
200200| One of those channels is archived | One of the managing channels is archived in Slack | Remove the archived channel, then try again |
201201| 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 |
202| The managed channel may have been made private or deleted | The managed channel was made private or deleted, or Claude is no longer in it | Check the channel in Slack. If it was made private, an Owner or Admin who is a member of it adds private managing channels again |
202| The managed channel may have been made private or deleted | The managed channel was made private or deleted, or Claude is no longer in it | Check the channel in Slack. If it was made private, an Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) who is a member of it adds private managing channels again |
203203| Claude isn't set up in the managed channel with its own channel configuration | The managed channel has no channel scope of its own on the **Slack** tab | [Add the channel](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel) in admin settings |
204204| The managed channel already has five managing channels | Five is the most a managed channel can have | Remove one before adding another |
205205| The file would be too large | The core instructions are over 16 KiB, or a reference file is over 100 KiB | Shorten the text, or move detail into a reference file |
claude-science/admin-controls Changed · +1 / -1 lines
from line 113
113113
114114Add skills for everyone in your organization in claude.ai, under **Organization settings** > **Skills** > **Organization skills**. Upload each skill as a .zip file. Members see it in the Claude Science app under **Settings** > **Skills**, in the **Organization** section. Organization skills go to every member. To update a skill, upload a new version in claude.ai.
115115
116To let members manage their own skills, host them in a GitHub repository. Put one `skills/<name>/SKILL.md` folder per skill in the repository and share the link. Members import them in the Claude Science app under **Settings** > **Skills** > **Add skill** > **Import from GitHub**. Claude Science records the commit each skill came from. **Check for updates** flags skills that are behind the repository's latest commit; each member chooses when to import again. Private repositories work after a member adds a GitHub token in the Claude Science app under **Settings** > **Credentials**.
116To let members manage their own skills, host them in a GitHub repository. Put one `skills/<name>/SKILL.md` folder per skill in the repository and share the link. Members import them in the Claude Science app under **Settings** > **Skills** > **Add skill** > **Import from GitHub**. Claude Science records the commit each skill came from. **Check for updates…** flags skills that are behind the repository's latest commit; each member chooses when to import again (see [Update skills imported from GitHub](/docs/claude-science/connectors-and-skills#update-skills-imported-from-github)). Private repositories work after a member adds a GitHub token in the Claude Science app under **Settings** > **Credentials**.
117117
118118To stop members from adding their own skills, turn off the **Allow custom skills** switch on the **Organization settings** > **Claude Science** page (see [Custom skills](#custom-skills)).
119119
claude-tag/admins/attach-to-scope Changed · +1 / -1 lines
from line 126
126126| Layer | Who writes it | Where |
127127| :- | :- | :- |
128128| Custom instructions | Owner for any scope; [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) for workspace and channel scopes; 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 |
129| Managed instructions | Full workspace members in one of the channel's [managing channels](/docs/claude-tag/admins/managed-by), which an Owner or a Claude Tag admin selects under **Managed by** on the channel's Configure page | By asking Claude in the managing channel and confirming the card it posts |
130130| Channel memory | Anyone in the channel | By telling Claude to remember |
131131| Task prompt | The requester | The message itself |
132132
claude-tag/admins/customize Changed · +1 / -1 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) |
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 a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) 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) |
2828| 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) |
2929| Plugins | Bundles of skills that teach Claude how to use a specific tool | [Attach plugins](/docs/claude-tag/admins/add-connections#attach-plugins) |
3030| Connections | Which systems it can reach from each channel | [Add connections](/docs/claude-tag/admins/add-connections) |
claude-tag/admins/restrict-access Changed · +2 / -2 lines
from line 361
361361
362362### What a channel manager can do on the Configure page
363363
364A channel manager has to be a member of the channel in Slack. The channel's [Configure page](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), which opens on claude.ai from the **Configure** link in any Claude reply, is split into tabs. In a channel you assigned to them, a channel manager sees the **Default model** card on the **General** tab and the repository and access bundle cards on the **Tools and access** tab. Members without the role don't see those cards. Owners and Admins also see an **Admin** tab, whose **Channel settings** card holds some of the channel scope's settings from admin settings.
364A channel manager has to be a member of the channel in Slack. The channel's [Configure page](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel), which opens on claude.ai from the **Configure** link in any Claude reply, is split into tabs. In a channel you assigned to them, a channel manager sees the **Default model** card on the **General** tab and the repository and access bundle cards on the **Tools and access** tab. Members without the role don't see those cards. Owners and [Claude Tag admins](#delegate-claude-tag-administration) also see an **Admin** tab, whose **Channel settings** card holds some of the channel scope's settings from admin settings.
365365
366366| Setting | What a channel manager can do |
367367| :- | :- |
from line 399
399399 </Step>
400400</Steps>
401401
402Owners and Admins can already configure every channel, so you see them as **Already has full access** and can't add them.
402Owners can already configure every channel, so you see them as **Already has full access** and can't add them.
403403
404404Leave the role as it was created: assigned to its channel, with **Claude Tag channel setup** as its only permission. If the role's permissions are changed on the Roles page, the channel's channel-managers popup stops recognizing the role and refuses to add or remove any, with a notice that points you to the Roles page. To recover, set the role's permissions back to exactly **Claude Tag channel setup**; the group and its members are kept. To give channel managers any other permission, create a separate role for it.
405405
claude-tag/users/good-habits Changed · +1 / -1 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 |
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 a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) sets it up | This channel |
169169| 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 |
170170| 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 |
171171