About delegating policy decisions to organizations
Policies can be defined for a whole enterprise, or set at the organization level. See directivas de GitHub Copilot para empresas y organizaciones.
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) | Indexación de repositorios para GitHub Copilot |
| Suggestions matching public code (privacy policy) | Most restrictive organization | Sugerencias de código de GitHub Copilot en tu IDE |
| Allow members without a Copilot license to use revisión de código Copilot in GitHub.com | Most restrictive organization | Tarjeta de aplicación: agentes de GitHub Copilot |
| Copilot can search the web | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
| Copilot Chat en GitHub Mobile | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
| Chat de Copiloto in the IDE | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
| Chat de Copiloto agent mode in the IDE | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
| revisión de código Copilot | Least restrictive organization | Tarjeta de aplicación: agentes de GitHub Copilot |
| agente en la nube de Copilot | Least restrictive organization | Tarjeta de aplicación: agentes de GitHub Copilot |
| Spark | Least restrictive organization | Tarjeta de aplicación: agentes de GitHub Copilot |
| Copilot in GitHub.com | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
| Copilot en GitHub Desktop | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
| CLI de Copilot | Least restrictive organization | Tarjeta de aplicación: agentes de GitHub Copilot |
| aplicación Copilot de GitHub | Least restrictive organization | Acerca del aplicación Copilot de GitHub |
| Editor preview features | Least restrictive organization | Términos de licencia de la versión preliminar de GitHub |
| MCP servers in Copilot | Least restrictive organization | Configuración de servidores MCP para el repositorio |
| Copilot-generated commit messages | Least restrictive organization | Tarjeta de aplicación: Copilot Chat de GitHub |
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