Who can configure content exclusion?
Why A is the answer
Repository admins, organization owners and enterprise owners
Those three roles can configure it, each at their own scope.
In detail
- Repository admins, organization owners and enterprise owners can configure it.
- Coordinate, so that rules do not conflict.
Use case
An illustrative scenario, not a real incident.
A repository admin adds an exclusion for their repository, while an enterprise owner sets one across the company.
See it in different ways
flowchart TD A["Content exclusion"] --> B["Applies: supported chat and completions"] A --> C["Applies: code review on GitHub"] A --> D["Not supported: Edit and Agent modes"] A --> E["Not guaranteed: third-party MCP servers"]
stateDiagram-v2 [*] --> Enterprise Enterprise --> Enabled: applies everywhere Enterprise --> Disabled: applies everywhere Enterprise --> Organizations: let organizations decide Organizations --> [*]
mindmap
root(("Content exclusion"))
n1["Repository"]
n2["Repository admins"]
n3["Organization"]
n4["Organization owners"]
n5["Enterprise"]
n6["Enterprise owners"]Key point: Admins and owners configure exclusions.
Why the other options are wrong
- B. Only GitHub support, after you open a ticket
- You do not need GitHub support.
- C. Only the person who first created the repository
- It is not limited to the creator.
- D. Any developer who has a Copilot seat
- A seat alone is not enough.