Learn about the policies that control the availability of GitHub Copilot features and models for users granted a license through your organization or an organization in your enterprise.
About policies for CopilotWhen you assign a Copilot license to a member of your organization, you can control the features they can use under that license with Copilot policies.
Policies are grouped into different types.
Each policy controls availability for members who receive a Copilot license from your enterprise or organization.
Organization-level control of policiesOrganization owners set policies to control the availability of features and models for users granted a Copilot license by the organization. For example, an organization owner can enable or disable using Copilot in the IDE (unless an enterprise owner has defined availability for the feature at the enterprise level).
The enforcement options for feature and model policies in an organization are:
For privacy policies, the options are called "Allowed" and "Blocked" in preference to enabled and disabled. This provides a clearer message of the impact of a privacy policy.
Enterprise-level control of policiesEnterprise owners can choose to set policies for Copilot at the enterprise level or to delegate the decision to organization owners using the No policy option.
If a policy is defined at the enterprise level, control of the policy is disabled at the organization level.
If organization owners are allowed to set a policy, some organizations may enable a feature while others disable it. If a member receives access to Copilot through multiple organizations with conflicting policies, either the least or most permissive policy may apply, depending on the policy. For more information, see Feature availability when GitHub Copilot policies conflict in organizations.
Next stepsRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4