About delegating policy decisions to organizations
Policies can be defined for a whole enterprise, or set at the organization level. See GitHub Copilot-Richtlinien für Unternehmen und Organisationen.
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 | Not applicable |
| Semantic indexing for non-GitHub repositories | Most restrictive organization (only available when all organizations explicitly set Enabled; Unconfigured behaves as disabled) | Indizierungsrepositorys für GitHub Copilot |
| Suggestions matching public code (privacy policy) | Most restrictive organization | GitHub Copilot-Codevorschläge in Ihrer IDE |
| Allow members without a Copilot license to use Copilot Codeüberprüfung in GitHub.com | Most restrictive organization | Anwendungskarte: GitHub Copilot Agents |
| Copilot can search the web | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
| Copilot Chat in GitHub Mobile | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
| Copilot-Chat in the IDE | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
| Copilot-Chat agent mode in the IDE | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
| Copilot Codeüberprüfung | Least restrictive organization | Anwendungskarte: GitHub Copilot Agents |
| Copilot-Cloud-Agent | Least restrictive organization | Anwendungskarte: GitHub Copilot Agents |
| Spark | Least restrictive organization | Anwendungskarte: GitHub Copilot Agents |
| Copilot in GitHub.com | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
| Der Copilot in GitHub Desktop | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
| Copilot CLI | Least restrictive organization | Anwendungskarte: GitHub Copilot Agents |
| GitHub Copilot App | Least restrictive organization | Über die GitHub Copilot App |
| Editor preview features | Least restrictive organization | Lizenzbestimmungen für die Vorabversion von GitHub |
| MCP servers in Copilot | Least restrictive organization | Konfigurieren von MCP-Servern für Ihr Repository |
| Copilot-generated commit messages | Least restrictive organization | Anwendungskarte: GitHub-Copilot Chat |
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