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 | Not applicable |
| 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 | IDE에서 GitHub Copilot 코드 제안 |
| 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 |
| GitHub Mobile의 Copilot Chat | 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 |
| GitHub Desktop의 Copilot 기능 | 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 시험판 사용 조건 |
| 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