Enterprise managed settings - GitHub Docs
Skip to main content Skip to content Collapse sidebar Expand sidebar Enterprise managed settings Understand the enterprise managed settings schema used by Copilot clients. In this article Use this reference to understand enterprise managed settings for Copilot. Most settings can be configured in managed-settings.json . Settings that require device management are noted below. For instructions on creating the file, see Getting started with enterprise-managed settings .
Supported keys Key Purpose permissions.disable Bypass Permissions Mode Disables bypass or YOLO-style allow-all behavior permissions.deny Blocks specific operations permissions.ask Requires a fresh human approval before specific operations can proceed permissions.allow Permits specific operations to proceed without a prompt permissions.disable Assisted Permissions Mode Prevents users from enabling assisted permissions permissions.default Mode Controls the default permission mode for new sessions features.computer Use Controls whether users can enable computer use features.browser Use Controls whether users can enable browser use model Sets your preferred model as the default for new conversations fusionTier Sets the default effort level for new conversations when the selected model is fusion autoTier Sets the default Auto routing tier for new conversations communication.support.url Sets an absolute http or https URL of an organization help page.
Informational only. Copilot CLI can link to it wherever it would otherwise tell users to contact their administrator enabledPlugins Enables or disables specific plugins by key extra Known Marketplaces Adds plugin marketplaces that users can access strict Known Marketplaces Restricts plugin installation to explicitly listed marketplaces telemetry Configures OpenTelemetry export, routing Copilot usage data to a collector of your choice remoteControl Restricts whether sessions hosted on this device can be remotely controlled, based on the controlling client's SSO authorization status for the listed organizations.
Doesn't affect the user's ability to remotely control sessions hosted on other devices force Remote Settings Refresh Requires a fresh server-managed settings fetch on client startup allowedMcpServers Defines an allowlist of MCP servers permitted to run. Any server not matched is blocked. Omit to allow all servers, subject to any deny rules deniedMcpServers Defines MCP servers that are unconditionally blocked, even if they also match an entry in allowedMcpServers sandbox Enforces minimum local sandbox restrictions for command execution, filesystem and network access, credentials, and local MCP and LSP servers.
Subject to minimum client version requirements. Client support by key Some keys require a minimum version in certain clients. See the footnotes in the table. Key Copilot CLI VS Code The GitHub Copilot app Copilot in the cloud (sandbox) Copilot in the cloud (GitHub Actions) JetBrains IDEs permissions.disable Bypass Permissions Mode permissions.deny permissions.ask permissions.allow permissions.disable Assisted Permissions Mode permissions.default Mode features.computer Use features.browser Use model fusionTier 1 2 3 4 autoTier 5 6 communication.support.url enabledPlugins extra Known Marketplaces strict Known Marketplaces telemetry remoteControl force Remote Settings Refresh allowedMcpServers deniedMcpServers sandbox 7 8 9 Support for telemetry varies by sub-property and harness.
See Capture controls for the clients that support fine-grained capture. More information on Copilot in the cloud Cloud sessions can run in sandboxes or on GitHub Actions. Coverage of policies and enterprise managed settings currently varies between environments. Where users can choose between these environments, cloud sandboxes are the default. However, currently, some interfaces can only run on GitHub Actions (such as assigning an issue to Copilot or mentioning @Copilot in a pull request).
The keys defined in the table for Copilot in the cloud (sandbox) are supported from all surfaces that support starting sessions in cloud sandboxes. As an exception, the model key is only supported for cloud sessions started from the GitHub website, Copilot CLI, and VS Code. allowedMcpServers and deniedMcpServers apply to MCP servers defined in user settings and repository settings, but don't apply to MCP servers defined in repository custom agent profiles.
However, you can prevent use of MCP servers configured in custom agent profiles by ensuring that any required domains to start them are not allowed by the organization or repository-level custom firewall. See Customizing or disabling the firewall for GitHub Copilot . Example configuration The following example shows these keys in one managed settings file. { "features" : { "computerUse" : false , "browserUse" : false } , "model" : "auto" , "autoTier" : "intelligence" , "permissions" : { "disableBypassPermissionsMode" : "disable" , "deny" : [ "Shell(rm -rf *)" , "Read(~/.ssh/**)" , "Edit(//etc/**)" , "Domain(*.unapproved.example)" ] , "ask" : [ "Shell(git push *)" , "Edit(/src/**)" , "Domain(api.github.com)" ] , "allow" : [ "Shell(npm test *)" , "Read(/src/**)" , "Domain(registry.npmjs.org)" ] } , "enabledPlugins" : { "my-plugin@agent-skills" : true } , "extraKnownMarketplaces" : { "agent-skills" : { "source" : { "source" : "github" , "repo" : "OWNER/REPO" } , "autoUpdate" : true } } , "strictKnownMarketplaces" : [ { "source" : "github" , "repo" : "OWNER/REPO" } ] , "telemetry" : { "enabled" : true , "endpoint" : "https://otel-collector.example.com" , "protocol" : "http/protobuf" , "capture" : { "identity" : true , "prompts" : false , "responses" : false , "toolArguments" : false , "toolOutput" : false , "policyDetail" : false } , "captureContent" : false , "lockCaptureContent" : true , "serviceName" : "copilot" , "resourceAttributes" : { "deployment.environment" : "production" } , "headers" : { "Authorization" : "Bearer TOKEN" } } , "remoteControl" : { "mode" : "requireSSO" , "githubDotComOrganizations" : [ "ORG-NAME" ] } , "allowedMcpServers" : [ { "serverUrl" : "https://api.githubcopilot.com/*" } , { "serverCommand" : [ "npx" , "@playwright/mcp@latest" ] } , { "serverCommand" : [ "cmd" , "/c" , "uvx" , "markitdown-mcp" ] } ] , "deniedMcpServers" : [ { "serverCommand" : [ "npx" , "-y" , "@modelcontextprotocol/server-filesystem" , "/" ] } ] , "sandbox" : { "enabled" : true , "failIfUnavailable" : true , "allowBypass" : false , "sandboxMcpServers" : true , "sandboxLspServers" : true } } features.computerUse Controls whether users can enable computer use in GitHub Copilot CLI and the GitHub Copilot app.
Set features.computerUse to false to prevent users from enabling computer use. A local setting cannot override this restriction. Set the value to true , or omit the key, to allow users to control computer use through their local settings. features.browserUse Note Browser use is in public preview and subject to change. Controls whether users can enable browser use in a Copilot surface. Set features.browserUse to false to prevent users from enabling browser use.
A local setting cannot override this restriction. Set the value to true , or omit the key, to allow users to control browser use through their local settings. enabledPlugins Defines plugins that are automatically installed or blocked for all enterprise users. Each entry uses the format PLUGIN-NAME@MARKETPLACE-NAME as the key, with a boolean value: true to require the plugin to be enabled, or false to require it to be disabled.
See About enterprise-managed plugin standards . Managed values always take precedence over repository defaults and member preferences. Repository defaults cannot enable a plugin that managed policy blocks or use a marketplace that policy disallows. extraKnownMarketplaces Defines additional plugin marketplaces available to users. Each entry is a named marketplace object containing a source property and an optional autoUpdate boolean.
Set autoUpdate
The rest of this page is on the live site.