GitHub Copilot allows setting default plugins at the team level
GitHub has added the ability for Copilot team administrators to select approved Agent Plugins as defaults for the entire team. The feature is available for Copilot Business and Enterprise.
GitHub has extended GitHub Copilot with team-level plugin customization. Team maintainers and organization owners can now select approved Agent Plugins and set them as defaults for the entire team, without every member having to go through the same configuration individually. The feature fills the gap between individual customization and policy applicable to the whole organization.
Configuration takes place via the \"Customize Copilot\" tab in the organizational team on github.com. The selected plugins are automatically enabled for direct team members in VS Code, in the GitHub Copilot app, and in Copilot CLI. According to the source, members of child teams do not inherit these settings. Team defaults are optional — users can turn off a specific plugin in the client if the organization's policy allows it.
Corporate and organizational policies always take precedence over team choices: Copilot clients continue to enforce which marketplaces are allowed and which plugins are mandatory or blocked, and team settings do not override these rules. The feature is available for the Copilot Business and Copilot Enterprise plans.
Why it matters
For teams using GitHub Copilot, this means less repeated individual configuration and a more consistent default set of tools (plugins) for all members. For companies, it is a way to standardize the use of the AI assistant within a team without having to change organizational policy — which remains the superior layer of control.
Two audiences, two different impacts
What this means
For individuals
Copilot users on a team can now receive preselected plugins automatically configured by an administrator, but depending on the organization's policy, they can turn them off in the client's settings (VS Code, app, CLI).
For a business
Team and organization administrators can standardize the default set of Agent Plugins for Copilot at the team level, reducing the administrative burden associated with repeated individual configuration, while corporate policies retain final control over which plugins are allowed and which are blocked.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.