About delegating policy decisions to organizations
Policies can be defined for a whole enterprise, or set at the organization level. See Политики GitHub Copilot для предприятий и организаций.
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 | Конечные точки REST API для метрик использования Copilot |
| Semantic indexing for non-GitHub repositories | Most restrictive organization (only available when all organizations explicitly set Enabled; Unconfigured behaves as disabled) | Индексирование репозиториев для GitHub Copilot |
| Suggestions matching public code (privacy policy) | Most restrictive organization | Предложения кода GitHub Copilot в вашем IDE |
| Allow members without a Copilot license to use Обзор кода Copilot in GitHub.com | Most restrictive organization | Карточка заявки: агенты GitHub Copilot |
| Copilot can search the web | Least restrictive organization | Заявка: GitHub Copilot Chat |
| Copilot Chat в GitHub Mobile | Least restrictive organization | Заявка: GitHub Copilot Chat |
| Копилот Чат in the IDE | Least restrictive organization | Заявка: GitHub Copilot Chat |
| Копилот Чат agent mode in the IDE | Least restrictive organization | Заявка: GitHub Copilot Chat |
| Обзор кода Copilot | Least restrictive organization | Карточка заявки: агенты GitHub Copilot |
| Copilot облачный агент | Least restrictive organization | Карточка заявки: агенты GitHub Copilot |
| Spark | Least restrictive organization | Карточка заявки: агенты GitHub Copilot |
| Copilot in GitHub.com | Least restrictive organization | Заявка: GitHub Copilot Chat |
| Copilot в GitHub Desktop | Least restrictive organization | Заявка: GitHub Copilot Chat |
| Второй пилот CLI | Least restrictive organization | Карточка заявки: агенты GitHub Copilot |
| приложение GitHub Copilot | Least restrictive organization | О приложении GitHub приложение Copilot |
| Editor preview features | Least restrictive organization | Условия лицензии GitHub Pre-release |
| MCP servers in Copilot | Least restrictive organization | Настройте MCP-серверы для вашего репозитория |
| Copilot-generated commit messages | Least restrictive organization | Заявка: 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