{"meta":{"title":"About enterprise-managed plugin standards","intro":"Enterprise administrators can centrally define plugin policies for users, ensuring consistent plugin availability.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/concepts","title":"Concepts"},{"href":"/en/copilot/concepts/agents","title":"Agents"},{"href":"/en/copilot/concepts/agents/about-enterprise-plugin-standards","title":"Enterprise plugin standards"}],"documentType":"article"},"body":"# About enterprise-managed plugin standards\n\nEnterprise administrators can centrally define plugin policies for users, ensuring consistent plugin availability.\n\nEnterprise-managed plugin standards allow administrators to **define and enforce policies for plugin availability**. By configuring a `managed-settings.json` file, administrators can specify which plugin marketplaces are available to users and which plugins are installed automatically.\n\n## Where plugin standards apply\n\nPlugin standards apply to all users on the enterprise's Copilot plan, across supported clients. See [Enterprise managed settings reference](/en/copilot/reference/enterprise-managed-settings-reference#supported-keys).\n\nUsers must upgrade to a supported client version for these standards to be applied.\n\n## How plugin standards work\n\nFor plugin standards, the `managed-settings.json` file can define:\n\n* **Known marketplaces**. Plugin marketplaces that are available to users for browsing and installing plugins.\n* **Default-enabled plugins**. Specific plugins that are automatically installed when users authenticate.\n\nWhen a user authenticates to Copilot in a supported client, the client queries the `managed-settings.json` file. The policies defined in the file are then applied to the user's session.\n\n## Why use enterprise-managed plugin standards\n\nEnterprise-managed plugin standards help administrators address several common challenges:\n\n* **Consistency across clients**. Ensure that all developers have access to the same plugins and marketplaces.\n* **Centralized governance**. Manage plugin availability from a single configuration file, rather than relying on individual developers to install the correct plugins.\n* **Version-controlled policies**. Because the configuration lives in a Git repository, all changes to plugin standards are tracked, auditable, and reviewable through pull requests.\n* **Reduced onboarding friction**. New developers automatically receive the enterprise's standard plugins when they authenticate, without any manual setup.\n\n## Next step\n\nTo configure enterprise plugin standards, see [Configuring enterprise-managed settings](/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings)."}