Playbooks · Teams
Set team plugin defaults for Copilot
Written November 19, 2026
Team maintainers can now set approved Copilot Agent Plugins as defaults for a GitHub team, on top of organization and enterprise policy.
A team that relies on the same Copilot plugins had to ask every member to repeat the same setup, one person at a time, and hope the results matched. The GitHub Changelog post of November 18, 2026 removes that repetition: team customizations are now generally available for organization teams. Team maintainers and organization owners can select approved Agent Plugins as team defaults, giving the team a shared starting point between individual customization and organization-wide policy. This page covers who can set the defaults, where, who actually receives them, and what still overrides them.
Who sets the defaults, and where
The post gives the setting job to team maintainers and organization owners. The steps start on github.com: open the organization team and select the Customize Copilot tab. From there, the maintainer works through the plugins and marketplaces described below and adds the plugins the team should start with. Nobody else in the team needs to visit the tab for the defaults to reach them, which is the point of setting them at team level rather than documenting a setup for each member to follow.
The defaults a maintainer can pick from are approved Agent Plugins. The word approved matters: this is a way to hand a team the plugins already sanctioned for its work, not a channel for any plugin a maintainer happens to like. What counts as approved is decided above the team, by the policy layers covered at the end of this page.
Marketplaces first, then plugins
From the Customize Copilot tab, the post says a maintainer can browse plugins from three sources: the marketplaces built into Copilot, the enterprise's marketplaces, and any marketplaces the team adds. A marketplace can be added from a GitHub repository that contains a plugin marketplace, which makes its plugins available to browse. Once the sources are in place, the maintainer adds individual plugins to the team to enable them.
The order is worth following as written. A plugin that lives in a marketplace the team has not added will not appear to browse, so a maintainer who cannot find an expected plugin should check the marketplace list before concluding the plugin is unavailable. Adding the repository first, then browsing, then adding the plugin is the sequence the post describes.
Who receives the defaults — and who does not
Selected plugins are enabled by default for the team's direct members, in VS Code, the GitHub Copilot app and Copilot CLI, per the post. The scope word is direct. Members of child teams do not inherit them. An organization that nests its teams — a parent team for a department, child teams for the groups inside it — cannot set defaults once at the parent and expect them to flow down. Each team whose members should start with the plugins needs its own defaults set by its own maintainer.
Team defaults are also optional for the people who receive them. Members can turn a team plugin off in their Copilot client where policy permits. A default here is a starting point handed to the team, not a setting locked onto every member's machine, and a maintainer who needs a plugin to be mandatory is asking for something this feature does not do.
What still overrides a team default
Enterprise and organization policies take precedence over team choices. The post is explicit that team defaults do not override those controls: Copilot clients continue to enforce which marketplaces are allowed and which plugins are required or blocked. So the layers stack in a fixed order. Policy at the enterprise and organization level decides what is permitted, required or blocked; team defaults choose a starting set inside what policy permits; the individual member can then turn a team plugin off where policy allows that too.
Team customizations are available for Copilot Business and Copilot Enterprise. This page is about distribution — getting approved plugins onto a team's machines by default. The opposite move, restricting customizations so they can only come from plugins at all, is a separate policy covered in Require Copilot customizations to come from plugins.
Related playbooks
- Set a spending policy before Copilot billing does
- Copilot Agent Merge: watch a PR and fix its blockers
- The Copilot app now takes GHES accounts
- Copilot Automations learn from real outcomes
Sources
- Customize GitHub Copilot for your team — GitHub Changelog — team customizations reaching general availability, maintainers and owners setting plugin defaults from the Customize Copilot tab, marketplaces, the direct-members-only scope, and enterprise and organization policy precedence.
Back to: Teams playbooks hub · Also: Require Copilot customizations to come from plugins