Clarify Copilot model policy precedence between enterprise and orgs#43956
Clarify Copilot model policy precedence between enterprise and orgs#43956luanzeba wants to merge 1 commit intogithub:mainfrom
Conversation
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
github-actions
Bot
added
the
triage
There was a problem hiding this comment.
Pull request overview
Clarifies how {% data variables.product.prodname_copilot_short %} policy conflicts are resolved when model policies are defined at both the enterprise and organization levels, especially for users licensed by multiple organizations.
Changes:
- Splits “feature/privacy” conflict behavior from “model policy” conflict behavior.
- Adds explicit bullets describing model policy precedence across enterprise vs. organizations.
- Updates the {% data variables.product.prodname_github_models %} table row to reflect enterprise-then-organization evaluation.
Show a summary per file
| File | Description |
|---|---|
| content/copilot/reference/policy-conflicts.md | Clarifies model policy precedence and updates the conflict-resolution table to match. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 2
| | {% data variables.copilot.copilot_cli_short %} | Least restrictive organization | [AUTOTITLE](/copilot/responsible-use/copilot-cli) | | ||
| | Editor preview features | Least restrictive organization | [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-pre-release-license-terms) | | ||
| | {% data variables.product.prodname_github_models %}, one policy per model | Least restrictive organization | [AUTOTITLE](/github-models/github-models-at-scale/manage-models-at-scale) | | ||
| | {% data variables.product.prodname_github_models %}, one policy per model | Most restrictive enterprise, then least restrictive organization | [AUTOTITLE](/github-models/github-models-at-scale/manage-models-at-scale) | |
| ## 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 {% data variables.product.prodname_copilot_short %} license. | ||
| Feature 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 {% data variables.product.prodname_copilot_short %} license. |
|
Never mind, this is already covered by the GitHub Models row. I think this PR is just making things more confusing. |
Why:
Closes: N/A
The policy conflict page explained organization-level conflict handling, but it did not explicitly call out how model policies combine enterprise and organization settings. This change clarifies that model policies are most restrictive at the enterprise level and least restrictive at the organization level.
What's being changed (if available, include any code snippets, screenshots, or gifs):
content/copilot/reference/policy-conflicts.mdto split feature/privacy behavior from model policy behavior.GitHub Models, one policy per modeltable row to reflect both levels of policy evaluation.Check off the following: