Enterprise administrators manage plugins from the Plugins and skills page in Organization settings. This page controls who in your organization can create plugins and holds the plugins your organization shares with its members. Connectors keep their own settings page, Organization settings → Connectors, and the permissions you set there apply inside every plugin.
If you are new to plugins, start with What are plugins?. For how members find and install plugins, see Find, install, and remove plugins.
Availability: Plugins are rolling out gradually, starting with individual plans and Self-Serve Enterprise organizations. Plugins are coming soon to sales-assisted Enterprise plans. Until then, members and admins keep using Connectors and Skills. If you don’t see Plugins in the sidebar yet, keep using Customize → Connectors and Skills. Everything there works as before.
Before you start
An administrator role in a Self-Serve Enterprise organization, or a custom role with permission to manage organization plugins.
A Self-Serve Enterprise organization that has the Plugins page (see Availability).
For uploads, a
.zipfile with aplugin.jsonmanifest at its root or in the Claude Code or Codex location. See Create or upload a custom plugin for the requirements.
How plugin permissions work
A plugin bundles connectors and skills, and it inherits the permissions of the connectors and skills inside it. In practice:
Connectors are governed on Organization settings → Connectors. The Enabled toggle and role access for each connector apply wherever the connector appears, including inside plugins. A plugin never grants access to a connector a member cannot otherwise use, and installing a plugin never connects an account on a member’s behalf. See Role-based access control for connectors.
Plugins and skills are governed on Organization settings → Plugins and skills, where you control who can upload or create plugins and skills and manage the organization’s library.
To stop members from using a particular tool, disable the connector. That turns it off everywhere, including inside every plugin that includes it. Members still see the plugin, and the connector inside it shows Disabled by your organization.
Set member permissions
On Organization settings → Plugins and skills, the permissions section has three controls:
Allow members to upload or create personal plugins and skills. Members can upload or import plugins, and create skills, for their own use.
Allow members to upload or create organization plugins and skills. Members can create plugins and skills shared with the organization. New organization plugins and skills appear on the Organization tab of the Plugins page in the sidebar for everyone and are uninstalled by default.
Allow members to install their own organization plugins and skills for everyone. Members can install organization plugins and skills they created for everyone without an admin approving the request. When this is off, members send a request and an admin decides.
If your organization uses custom roles, you can grant plugin permissions to specific roles on the Roles & Permissions page. See Enterprise roles and permissions.
Members cannot create organization connectors, including by uploading a plugin that declares a new connector. Plugins created by members can only reference connectors that already exist in your organization.
Publish an organization plugin
The Organization plugins and skills section lists every plugin shared with your organization. Publishing a plugin makes it available on the Organization tab for members to install themselves. Installing it for everyone is a separate step.
Open Organization settings → Plugins and skills
Only people who can manage organization plugins see this page.
Select Upload plugin
Upload a .zip file with a plugin.json manifest at its root or in the Claude Code or Codex location. Uploading here publishes the plugin to your organization’s library. See Create or upload a custom plugin for the file requirements and limits.
Review the plugin
Open the plugin to confirm its skills and connectors were imported as expected. The plugin’s page opens in Plugins and skills, where you can also turn individual bundled skills on or off.
Members who are allowed to create organization plugins can also publish a personal plugin to the organization from the Plugins page in the sidebar. A published plugin moves to the organization’s library and is not installed for anyone automatically.
Install a plugin for everyone
Installing a plugin for everyone puts it on every member’s Installed tab and installs its skills for each member. Members still connect each connector with their own account.
Open the plugin from Organization plugins and skills
On Organization settings → Plugins and skills, find the plugin in the Organization plugins and skills list and open it.
Select Install org-wide
The plugin is installed for everyone in your organization. You can also install it for everyone from the list by selecting the plus (+) button on its card.
To remove the plugin for everyone, open it from the same list and select Uninstall.
Members can also ask for a plugin they created to be installed for everyone by selecting Request org install on the plugin. If members are allowed to install their own organization plugins for everyone, the plugin is installed right away and a confirmation reads Installed for your organization. Otherwise, a confirmation reads Request sent to admins, and an administrator completes the installation from the organization’s plugin library.
How to verify it worked
In the Organization plugins and skills list, the plugin’s card shows a check mark instead of the plus (+) button, and members see the plugin on their Installed tab. Connectors inside it still show Connect for each member until they connect their own account.
What members see
In Discover, connectors a member can’t use appear dimmed, with the reason on hover.
The Organization tab shows plugins, skills, and connectors your organization has shared.
Inside a plugin, each connector shows its own status: Connect, Connected, Reconnect, Disabled by your organization, Unavailable (not available to the member’s account, usually because their role does not have access), or Upgrade required (the plan does not include the connector). The plugin stays visible and its other components keep working.
Audit logs
Connector connections and disconnections are recorded in your organization’s audit logs. Plugin and skill installation events are not logged separately.
Related articles
Need more help?
Reach out to your account team or contact us via Help > Contact Support. Visit the Trust Center for security and compliance documentation.