Question

A team lead on the GitHub Copilot Business plan wants to configure content exclusions so that a sensitive configuration directory is never used as context by Copilot. When they navigate to their organization settings, they discover the content exclusion configuration option is not available. What is the most likely reason?

Accepted Answer

The team lead is signed in with a GitHub Copilot Individual (personal) subscription rather than a Business or Enterprise plan, and content exclusions are not offered on individual plans.

Answer

Content exclusions are only configurable by repository administrators, not organization owners, so the team lead lacks the required permission level.

Answer

Content exclusions must first be requested through GitHub Support before the setting appears in the organization UI.

Answer

The organization has not yet enabled the public code matching filter, which is a prerequisite for content exclusions.