GitHub Copilot team customizations reach general availability, letting teams share default plugins

Team maintainers and organization owners can now pick approved Agent Plugins as defaults, enabled for direct team members in VS Code, the GitHub Copilot app and Copilot CLI.

Share

Published 2 min read

Promotional image: Customize GitHub Copilot for your team
Image: Divulgação/GitHub

In brief

  • Team customizations for GitHub Copilot are generally available for organization teams, published November 18, 2026, at 4:00 PM UTC.
  • Maintainers and owners choose approved Agent Plugins as team defaults, so members skip repeating the same setup.
  • Enterprise and organization policies still take precedence, and members of child teams do not inherit the defaults.
  • The feature is available on Copilot Business and Copilot Enterprise.

GitHub announced on November 18, 2026, at 4:00 PM UTC that team customizations for GitHub Copilot are generally available for organization teams. Team maintainers and organization owners can now select approved Agent Plugins as team defaults, so members no longer have to repeat the same setup one by one.

The selected plugins are enabled by default for direct team members in VS Code, the GitHub Copilot app and Copilot CLI. The feature is available on Copilot Business and Copilot Enterprise.

What changes for teams

  • Team customizations are generally available for organization teams.
  • Maintainers and organization owners can choose approved Agent Plugins as team defaults.
  • Default plugins are on for direct members in VS Code, the GitHub Copilot app and Copilot CLI.
  • Members of child teams do not inherit the team's default plugins.
  • Team defaults are optional, and enterprise and organization policies take precedence.

Setting up plugins for a team

Team maintainers and organization owners start by opening their organization team on github.com and selecting the Customize Copilot tab. From there they can browse plugins from the marketplaces built into Copilot, from their enterprise's marketplaces and from any marketplaces the team has added, then add individual plugins to the team.

A team can also add its own marketplace from a GitHub repository that contains a plugin marketplace. Doing so makes that marketplace's plugins available to browse, and individual plugins still have to be added to the team to be enabled.

Team defaults are optional. Where policy allows it, members can turn off a team plugin in their own Copilot client.

Existing policies still apply to team defaults

Enterprise and organization policies take precedence over team choices. Copilot clients continue to enforce which marketplaces are allowed and which plugins are required or blocked, and team defaults do not override those controls.

One limit on reach: members of child teams do not inherit the default plugins set for the parent team. Only direct team members get them enabled by default.

Share

How this story was made

Drafted with the help of artificial intelligence from a fact sheet built on the sources listed below. Software checked its numbers, dates and names against that fact sheet, and Vynuo, the editor in charge, approved the text before it was published.

Sources for this story

How we know: information from an official source (GitHub), checked on November 18, 2026.

  1. OfficialCustomize GitHub Copilot for your team (opens in a new tab)GitHub, accessed November 18, 2026

Topics