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 |
| Copilot CLI (コパイロット 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