GitHub Previews Team-Level Copilot Model Controls for Enterprises
The new policy mode lets administrators keep a company-wide baseline while granting additional models to selected enterprise teams.
GitHub introduced a public preview of team-level model access controls for GitHub Enterprise customers using Copilot Business or Copilot Enterprise on July 31, 2026. Administrators can establish an enterprise-wide baseline and then make additional models available to selected enterprise teams, shifting part of Copilot governance from resources to users.
What changed
The new enterprise teams mode gives model policies three states. Enabled models are available to everyone in the enterprise, Disabled models are unavailable to everyone, and Optional models can be assigned to particular enterprise teams. GitHub says most enterprise customers will gain access to the preview opt-in on August 3 as the rollout proceeds gradually.
That structure is designed for cases where model access should follow a role, training level or function. An enterprise could keep a broadly approved set available to all licensed users while allowing a smaller evaluation team to try an additional model without opening it to the entire organization.
The access calculation is deliberately permissive across team memberships. If any enterprise team grants a user a model, that user can access the model everywhere while working under a Copilot license from that enterprise. Administrators therefore need to review overlapping team membership, because one grant can outweigh a more restrictive assignment elsewhere.
Migration and rollback
Organizations can create enterprise teams and assign Optional models before switching on enterprise teams mode. GitHub presents that staging period as a way to prepare assignments before the new policy path becomes authoritative.
Once the mode is enabled, model access is managed at the enterprise and enterprise-team levels; organization-level model settings stop applying. During the preview, an administrator can roll back and restore the previous policy configuration. For users licensed through more than one enterprise, GitHub says only the policies of the enterprise supplying the active Copilot license apply.
Why it matters
The preview separates a company's default model catalogue from exceptions for specific groups. That can reduce the pressure to choose between opening an experimental model to everyone and blocking it completely. It also creates a new governance boundary: access decisions now depend on enterprise-team membership and license provenance, not only the organization that owns a repository.
The feature is still a preview and is rolling out gradually. GitHub has not published adoption data, audit outcomes or evidence that team-level targeting reduces policy mistakes. Administrators should map memberships and test rollback before treating the preview as a durable control layer.
Status
Confirmed. GitHub announced the preview and its policy behavior in the official changelog. Internal confidence is medium because implementation details come from one first-party source and have not been independently corroborated.
Sources
Update note: Last reviewed 2026-07-31. We will revise this post if GitHub changes rollout timing, access evaluation or rollback behavior.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.