Feature availability when GitHub Copilot policies conflict in organizations
Delegating Copilot policy decisions to organizations affects users granted a license by organizations with different policies.
About delegating policy decisions to organizations
Policies can be defined for a whole enterprise, or set at the organization level. See AUTOTITLE.
When an enterprise owner delegates control of a policy to organization owners by setting "No policy," some organizations may enable a feature while others disable it. Users may be granted a Copilot license by organizations with different policies for the same feature.
How availability is determined
Feature, model, and privacy settings for users are set according to the least restrictive or the most restrictive policy defined by any of the organizations where they are granted a Copilot license.
-
Least restrictive: if any of the organizations has enabled a feature, this feature is enabled for the user everywhere. This applies to all but the more sensitive Copilot features.
-
Most restrictive: if any of the organizations has disabled a feature, this feature is disabled for the user in all their organizations. This applies only to the most sensitive Copilot features, for example: access to Copilot metrics using the API.
Availability for members with Copilot from multiple organizations
| Policy | Availability matches | More information |
|---|---|---|
| Copilot Metrics API | Most restrictive organization | AUTOTITLE |
| Semantic indexing for non-GitHub repositories | Most restrictive organization (only available when all organizations explicitly set Enabled; Unconfigured behaves as disabled) | AUTOTITLE |
| Suggestions matching public code (privacy policy) | Most restrictive organization | AUTOTITLE |
| Allow members without a Copilot license to use Copilot code review in GitHub.com | Most restrictive organization | AUTOTITLE |
| Copilot can search the web | Least restrictive organization | AUTOTITLE |
| Copilot Chat in GitHub Mobile | Least restrictive organization | AUTOTITLE |
| Copilot Chat in the IDE | Least restrictive organization | AUTOTITLE |
| Copilot Agent Mode in IDE Chat | Least restrictive organization | AUTOTITLE |
| Copilot code review | Least restrictive organization | AUTOTITLE |
| Copilot cloud agent | Least restrictive organization | AUTOTITLE |
| Spark | Least restrictive organization | AUTOTITLE |
| Copilot in GitHub.com | Least restrictive organization | AUTOTITLE |
| Copilot in GitHub Desktop | Least restrictive organization | AUTOTITLE |
| Copilot CLI | Least restrictive organization | AUTOTITLE |
| GitHub Copilot app | Least restrictive organization | AUTOTITLE |
| Editor preview features | Least restrictive organization | AUTOTITLE |
| MCP servers in Copilot | Least restrictive organization | AUTOTITLE |
| Copilot-generated commit messages | Least restrictive organization | AUTOTITLE |
Availability for members with Copilot from multiple enterprises
If a user receives a license from multiple different enterprises, the most restrictive policy usually applies. The exceptions are:
- AI credit paid usage (this applies to each enterprise, not the user)
- GitHub Spark