We’re introducing a new global default policy for generally available GitHub Copilot features and supported client capabilities in enterprise and organization Copilot settings. For the next 28 days, you can configure this policy, but it won’t affect feature access for your users yet.
What’s changing #
Today, you can configure the new policy by going to the “AI Controls” page, opening the “Copilot” subpage, and selecting an option under “Default policy for new features”. This policy applies to eligible features managed on your enterprise’s “Features & clients” page (i.e., https://github.com/enterprises/YOUR-ENTERPRISE-SLUG/ai-controls/copilot/features), as well as the Copilot Code Review policy on the “Agents” page and the MCP servers in Copilot policy. For feature eligibility and exceptions, see our docs on default availability.
You can choose from the following settings:
- Enabled : Current and future eligible features will be available to users by default.
- Disabled : Current eligible features will remain unavailable, and future eligible features will require administrator approval.
- Let organizations decide : Organization administrators can choose whether to enable or disable eligible features.
Starting October 22, the policy takes effect. At that point:
- Eligible generally available features and capabilities left Unconfigured will follow your selected global default of enabled, disabled, or let organizations decide.
- Explicit decisions are preserved. If you’ve explicitly enabled or disabled a feature, we won’t override that choice.
- Preview features remain opt-in. If you opt into a preview and it later becomes generally available, your existing choice will be preserved.
Join the discussion within GitHub Community.