If a teammate cannot see the Copilot plugin you selected for your team, check direct team membership first. GitHub’s new team defaults apply to direct members, and members of child teams do not inherit them. Next, check the client and your organization’s policies. Those details can explain why two people in the same broader group have different setups.

GitHub announced general availability of team customizations on November 18, 2026 for Copilot Business and Enterprise. The feature lets maintainers choose plugins that give teammates a shared starting point. Here is a practical way to introduce one plugin and check who receives it.
Choose one recurring task
Start with a plugin that supports work your team already repeats, such as preparing release notes. Write down the expected result and choose someone to maintain the setup. Before sharing it, review what the plugin contains. GitHub’s plugin documentation explains how plugins package customizations. A package can bring capabilities that deserve a closer look, especially when it connects tools or runs scripts. Ask the person who will own the setup to review those components before teammates use them.
Add the plugin from the team page
A team maintainer or organization owner can open the organization team on GitHub.com and select Customize Copilot. From there, browse an available marketplace and add the individual plugin to the team. If you add a marketplace repository, choose the plugin within it that you want to enable. Keep a short note of the marketplace and plugin name so another maintainer can find the same selection.
Check a missing default in order
Confirm that the person is a direct member of the team where you made the selection. For example, someone who belongs only to a child team will need the setup addressed for that team or through another approved arrangement. Then check whether they are using VS Code, the Copilot app or Copilot CLI, which GitHub lists for these team defaults.
If membership and client match, ask the organization administrator to check allowed marketplaces and required or blocked plugins. Enterprise and organization policy takes precedence over team choices. Members can also turn off an optional team plugin in their client where policy permits. Have the teammate inspect its current state before assuming the team selection failed.
Verify the shared workflow with an example
Once the plugin appears, use a small sample task to check that it does what your team expects. For a release-notes plugin, try fictional completed and open work items and inspect which ones reach the output. Our first Copilot Evals guide shows how to turn that kind of requirement into a repeatable check. Record the selection, the task and the result in your team’s setup notes. Revisit that example when you change the plugin so the next maintainer has something concrete to compare.
Prepared with AI assistance from GitHub’s launch announcement and plugin documentation. The release-notes example is illustrative. TechPulse did not test a team deployment. See our editorial policy.
✍️ Leave a Comment