About delegating policy decisions to organizations
Policies can be defined for a whole enterprise, or set at the organization level. See stratégies de GitHub Copilot pour les entreprises et les organisations.
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 | Points de terminaison d’API REST pour les métriques d’utilisation Copilot |
| Semantic indexing for non-GitHub repositories | Most restrictive organization (only available when all organizations explicitly set Enabled; Unconfigured behaves as disabled) | Indexation de référentiels pour GitHub Copilot |
| Suggestions matching public code (privacy policy) | Most restrictive organization | Suggestions de code GitHub Copilot dans votre IDE |
| Allow members without a Copilot license to use révision du code Copilot in GitHub.com | Most restrictive organization | Carte d’application : agents GitHub Copilot |
| Copilot can search the web | Least restrictive organization | Carte d’application : GitHub Copilot Chat |
| Copilot Chat dans GitHub Mobile | Least restrictive organization | Carte d’application : GitHub Copilot Chat |
| Discussion avec Copilot in the IDE | Least restrictive organization | Carte d’application : GitHub Copilot Chat |
| Discussion avec Copilot agent mode in the IDE | Least restrictive organization | Carte d’application : GitHub Copilot Chat |
| révision du code Copilot | Least restrictive organization | Carte d’application : agents GitHub Copilot |
| Agent cloud Copilot | Least restrictive organization | Carte d’application : agents GitHub Copilot |
| Spark | Least restrictive organization | Carte d’application : agents GitHub Copilot |
| Copilot in GitHub.com | Least restrictive organization | Carte d’application : GitHub Copilot Chat |
| Copilot dans GitHub Desktop | Least restrictive organization | Carte d’application : GitHub Copilot Chat |
| Copilot pour CLI | Least restrictive organization | Carte d’application : agents GitHub Copilot |
| GitHub application Copilot | Least restrictive organization | À propos de l’application GitHub Copilot |
| Editor preview features | Least restrictive organization | GitHub – Termes du Contrat de licence de la préversion |
| MCP servers in Copilot | Least restrictive organization | Configurer des serveurs MCP pour votre référentiel |
| Copilot-generated commit messages | Least restrictive organization | Carte d’application : 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