← All permissions
Organization permission·org_copilot_content_exclusion:write
Copilot content exclusion: Write
Tier 2 · Medium
Why Tier 2
Changes which files Copilot must ignore, so sensitive files can be put back in reach of Copilot.
Management plane permissions start at Tier 1. This one is lowered for the reason above.
- Target
- Organization
- Plane
- ManagementOrganization policy: Org and enterprise settings, rulesets, Actions policy, custom properties and Copilot controls.
- Granted by
- Fine-grained PAT, GitHub App
- Available on
- Free, Team, Enterprise Cloud, EMU
What it unlocks
1 REST endpoint needs this permission. A few of them:
- PUT /orgs/{org}/copilot/content_exclusion
Roles that include it
No built-in role includes it. Only tokens, Apps or custom roles can grant it.
Classic scopes that reach it
No classic scope reaches it. Only fine-grained PATs, Apps or GITHUB_TOKEN can grant it.
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.
Other levels
GitHub Docs: Organization permissions for "Copilot content exclusion"