Admin controls changedclaude-science/admin-controls
Nearest release: v2.1.302, published an hour 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 16 Oct 2026 15:19 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 16 Oct 2026 15:37 UTC.
Upstream edited
Recorded here
Lines+16added
Lines−4removed
From line
61
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits23to this page, all time
The whole hunk
from line 61, old and new numbered
/
from line 61
6161
6262Turning on the **Claude Science** capability in a role also turns on the seven under it, and you can then turn off the ones that role shouldn't have. Any capability whose control your organization can't turn on stays off. Turning the **Claude Science** capability off turns them all off. A role whose **Capability access** setting is **All capabilities** already includes all seven. A role set to **All generally available** gets them when you turn on its **Claude Science** capability (see [Who gets access after you enable](/docs/claude-science/enable-claude-science#who-gets-access-after-you-enable)).
6363
64<Note>
65 Giving a custom role the **Claude Science** capability gives its members the app. For skills from claude.ai and your organization's plugins to reach those members, their custom roles also need one of the capability options listed under [Organization skills](#organization-skills).
66</Note>
67
6468For a member whose custom roles don't include a capability, the feature behaves as it does when you turn its control off (see [How changes reach members](#how-changes-reach-members)). The setting is grayed out in the Claude Science app, and what the member set up earlier is kept. To give that member the feature, turn on the capability in one of their roles. A change to a role's capabilities can take up to 15 minutes to reach members, and then applies on the member's next turn or request.
6569
6670The network allowlist, the package mirror, Modal workspaces, and the switches for Featured connectors and skills aren't set by role and apply to the whole organization. To create custom roles and assign them to groups, see [Manage custom roles on Enterprise plans](https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans).
from line 115
111115
112116### Organization skills
113117
114Add 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.
118To add skills for your organization, go to [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory) in claude.ai and follow [Provision and manage skills for your organization](https://support.claude.com/en/articles/13119606-provision-and-manage-skills-for-your-organization) in the help center. Skills you add with **Upload a skill** or **Create a skill** appear in the Claude Science app under **Settings > Skills**, in the **Organization** section, for the members who have them turned on. A skill you upload is turned on for everyone by default. On Enterprise plans, if you give skills to specific groups through a plugin, the app gets them only when the plugin is **Installed by default** or **Required** for that group (see the plugins row under [Connectors](#connectors)). To update a skill, go to [**Organization settings > Plugins & skills > Inventory**](https://claude.ai/admin-settings/skills?tab=inventory), open the menu at the end of the skill's row, and select **Upload new version**.
115119
120Skills from claude.ai are the ones you add on the **Plugins & skills** page, the ones members have in their own claude.ai accounts, and ones shared with them. For skills from claude.ai and your organization's plugins to reach a member's app, the **Skills** switch in the **Policy** tab of **Plugins & skills** has to be on. Members in the built-in roles (User, Admin, Owner, and Primary Owner) need nothing more, whether your organization's **Cloud code execution and file creation** setting is on or off. A member whose role is set to **Custom** also needs one of these options in their custom roles:
121
122* The **Claude Code** capability.
123* The **Cowork** capability, which counts only while Cowork is turned on for your organization.
124* The **Chat** and **Code execution and file creation** capabilities together, which count only while **Cloud code execution and file creation** is turned on. **Code execution and file creation** is the capability in the role, listed under **Chat**, and **Cloud code execution and file creation** is your organization's setting (see its row under [Capability toggles](#capability-toggles)).
125
126Without one of these options, no skills from claude.ai and none of your organization's plugins reach that member's app. To give the member one, turn it on in the **Capabilities** tab of one of their custom roles (see [Capabilities in custom roles](#capabilities-in-custom-roles)). If your organization keeps **Cloud code execution and file creation** off, the **Chat** and **Code execution and file creation** option has no effect. Choose **Claude Code**, or **Cowork** if Cowork is turned on for your organization.
127
116128To 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. When the repository has new commits, **Check for updates…** flags the skills whose files differ from its 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**.
117129
118130To 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)).
from line 241
229241| Claude Science > Enable for your organization | Supported in Claude Science | Off by default for Team and Enterprise, and on by default for the Claude Team plan for scientists. An Owner or Primary Owner turns it on or off under **Organization settings** > **Claude Science** (see [Enable Claude Science](/docs/claude-science/enable-claude-science)). Assigning seats doesn't turn it on. |
230242| Data and privacy > Rate chats | Supported in Claude Science | When you turn this off, the app hides the **Send feedback** link on the [**Chat paused**](/docs/claude-science/safeguards#when-safeguards-flag-a-message) card. If your organization uses customer-managed encryption keys (CMEK), you can't turn this setting on and the app doesn't show that link. |
231243| Organization and access > Organization instructions | Supported in Claude Science | Anthropic adds your organization instructions to the app's requests to Claude, as it does for claude.ai chat, so members don't need to update the app for a change to apply. |
232| Skills > Organization skills and Policy | Supported in Claude Science | Skills you add under **Organization skills**, and members' own claude.ai skills, appear in Claude Science while **Skills** is on, and **User-created skills** decides whether a member can save a skill from the app to their own claude.ai account. The skills that come with the app and the skills members add in it are controlled on the **Claude Science** page: one switch per Featured skill, and **Allow custom skills** for skills members add themselves (see [Featured connectors and skills](#featured-connectors-and-skills) and [Custom skills](#custom-skills)). |
244| Plugins & skills > skills you add for your organization, and the Policy tab | Supported in Claude Science | The **Skills** switch in the **Policy** tab has to be on for Claude Science to get your organization's plugins and to get skills from claude.ai. Skills from claude.ai include the ones you add for your organization. A member whose role is set to **Custom** also needs one of the capability options listed under [Organization skills](#organization-skills). **User-created skills**, on the same tab, decides whether a member can publish a skill from the app to their own claude.ai account. Publishing one also needs **Cloud code execution and file creation** to be on (see its row under [Capability toggles](#capability-toggles)). The skills that come with the app and the skills members add in it are controlled on the **Claude Science** page: one switch per Featured skill, and **Allow custom skills** for skills members add themselves (see [Featured connectors and skills](#featured-connectors-and-skills) and [Custom skills](#custom-skills)). |
233245| Capabilities > Web search | Not applicable in Claude Science | This setting governs claude.ai chat. Claude Science can search the web regardless of it, and the **Claude Science** page has no switch for web search. |
234| Capabilities > Code execution and file creation | Not applicable in Claude Science | This setting governs the code sandbox Anthropic hosts for claude.ai chat. Running code on the member's computer, or on compute the member connects, is the core of Claude Science and can't be turned off; you govern what that code can reach with the [network allowlist](#network-allowlist), [SSH hosts](#ssh-hosts), and [Modal](#modal) controls. |
246| Capabilities > Cloud code execution and file creation | Partially supported in Claude Science | This setting governs the code sandbox Anthropic hosts for claude.ai chat. Running code on the member's computer, or on compute the member connects, is the core of Claude Science and can't be turned off; you govern what that code can reach with the [network allowlist](#network-allowlist), [SSH hosts](#ssh-hosts), and [Modal](#modal) controls. In the app, a member needs this setting turned on to publish a skill to their claude.ai account or to delete a published one. For a member whose role is set to **Custom**, this setting is also part of one capability option for getting skills from claude.ai and your organization's plugins (see [Organization skills](#organization-skills)). |
235247| Capabilities > Allow network egress and Domain allowlist | Supported in Claude Science | These settings govern the hosted sandbox for claude.ai chat. Claude Science's sandbox has its own allowlist: manage it for the whole organization with the **Manage network allowlist** switch on the **Claude Science** page (see [Network allowlist](#network-allowlist)), or leave it off and let members manage their own. Administrators can also extend a member's list per device with the sandbox network keys in the [configuration file reference](/docs/claude-science/configuration-file-reference). |
236248| Data and privacy > Location metadata | Not applicable in Claude Science | Claude Science doesn't send location data with requests to Claude, so there is nothing for this setting to govern. |
237249| Capabilities > Memory (Enable memory for your team) | Supported in Claude Science | This setting governs memory in claude.ai chat. Claude Science keeps a separate memory on each member's computer, which you turn on or off with the **Turn on memory for your team** switch on the **Claude Science** page (see [Memory](#memory)). On Enterprise plans, a custom role's **Memory** capability under **Claude Science** can limit it to certain roles (see [Capabilities in custom roles](#capabilities-in-custom-roles)). |
from line 255
243255| - | - | - |
244256| Connectors > connectors you add for your organization | Supported in Claude Science | Connectors you add on the **Connectors** page, from the directory or by web address (custom connectors), are available to members in the app, as in claude.ai. Claude connects to them from Anthropic's servers, and members sign in with their own accounts where needed. |
245257| Roles > connector permissions in custom roles (Enterprise) | Partially supported in Claude Science | Apply to the connectors on your **Connectors** page, which the app reaches through Anthropic. They don't apply to the Featured connectors that run on members' computers or to custom connectors members add in the Claude Science app. The **Claude Science** page controls those Featured connectors for every member. The **Allow custom connectors** switch there decides whether members can add and use custom connectors, and a separate capability in custom roles, **Custom connectors**, can limit that to certain roles (see [Capabilities in custom roles](#capabilities-in-custom-roles)). |
246| Plugins > plugins you add for the organization | Partially supported in Claude Science | Plugins you set to **Installed by default** or **Required** are synced to members' Claude Science app, which loads their skills and connectors. A plugin's connector prompts each member for approval per tool, and its interactive output doesn't open in the app. Plugins left as **Available to install** aren't offered in the app, and plugin commands don't apply there. Which Featured connectors and skills members can use, and whether they can add their own, are separate controls on the **Claude Science** page (see [Featured connectors and skills](#featured-connectors-and-skills), [Custom connectors](#custom-connectors), and [Custom skills](#custom-skills)). |
258| Plugins & skills > plugins you add for your organization | Partially supported in Claude Science | Plugins you set to **Installed by default** or **Required** are synced to members' Claude Science app, which loads their skills and connectors. The **Skills** switch in the **Policy** tab has to be on for this sync. A member whose role is set to **Custom** also needs one of the capability options listed under [Organization skills](#organization-skills). A plugin's connector prompts each member for approval per tool, and its interactive output doesn't open in the app. Plugins left as **Available to install** aren't offered in the app, and plugin commands don't apply there. Which Featured connectors and skills members can use, and whether they can add their own, are separate controls on the **Claude Science** page (see [Featured connectors and skills](#featured-connectors-and-skills), [Custom connectors](#custom-connectors), and [Custom skills](#custom-skills)). |
247259| Connectors > Tunnels API (Enterprise) | Partially supported in Claude Science | A connector your organization serves through a tunnel works in the app the same way it does in claude.ai, because the app reaches the connectors on your **Connectors** page through Anthropic's hosted connector service. Custom connectors a member adds in the Claude Science app connect directly from the member's computer and never use a tunnel (admins can restrict this in [Custom connectors](#custom-connectors)). |
248260| Connectors > connectors members add themselves | Supported in Claude Science | In claude.ai, members use only the connectors on your **Connectors** page. In Claude Science, members can also add custom connectors (a server URL or a local command) while the **Allow custom connectors** switch is on, which it is by default for Team and not for Enterprise, and the **Connectors** page and its restrictions don't apply to those. Turn off the **Allow custom connectors** switch under **Organization settings** > **Claude Science** to limit members to Featured connectors and the connectors you add on your **Connectors** page (see [Custom connectors](#custom-connectors)). On Enterprise plans, you can also leave the switch on and limit custom connectors to certain custom roles (see [Capabilities in custom roles](#capabilities-in-custom-roles)). |
249261| Connectors > Desktop extension allowlist | Not applicable in Claude Science | Claude Science doesn't install desktop extensions, so there is nothing for this setting to govern. |
No line in this hunk matches that.