Teams in an enterprise

What are teams?

Teams are groups of users in an enterprise or organization. By creating teams, you can manage users at scale and simplify access, licensing, and communication. For example, you could create an auditor team for users who need access to audit logs, or a Copilot team for users who receive Copilot licenses.

Enterprise teams are managed at the enterprise level and can include users from across the enterprise and its organizations. With enterprise teams, you can centralize administration and manage organization access, roles, and licensing at scale.

Organization teams are managed at the organization level and can only include members of a single organization. There are certain features of organization teams that are not currently supported for enterprise teams, such as CODEOWNER status.

Can I manage teams from an identity provider?

If you have integrated GitHub with an identity provider (IdP), you can link teams on GitHub with groups in your IdP. When membership of the IdP group changes, the change is reflected in the GitHub team, allowing you to centralize access management.

The capabilities of this feature depend on whether you use Enterprise Managed Users or personal accounts.

Enterprise Managed Users

You can make changes to IdP groups to manage repository access, add or remove users from organizations, or grant or remove GitHub Copilot licenses. For example, if a new user is added to an IdP group that is linked to a team with access to an organization, the user receives access to that organization. For more information, see ID プロバイダー グループを使用したチーム メンバーシップの管理.

This feature is available with both enterprise and organization teams.

Personal accounts

Team synchronization allows you to centrally manage any privileges linked to an organization team, such as repository access and CODEOWNER status. However, team sync cannot be used to add users to organizations where they don't already have access. For more information, see Enterprise で Organization の Team 同期を管理する.

Team sync with personal accounts is only available with organization teams, and you must use Entra ID or Okta as an IdP.

What kind of team should I use?

To simplify administration at scale, GitHub recommends using enterprise teams for any use cases that apply to the enterprise account or to multiple organizations. Organization teams are useful when the need for the team is scoped to a single organization and the team can be managed by an organization administrator.

You may need to create organization teams if the functionality you need is not covered by enterprise teams. GitHub plans to address some limitations in the near future.

Enterprise teams can:

• Receive Copilot Business licenses directly from the enterprise.
• Be assigned predefined and custom enterprise roles, giving members access to enterprise settings.
• Be added to organizations, where organization administrators can grant the team additional access and permissions.
• Receive bypass access on rulesets.

However, unlike organization teams, enterprise teams currently do not support:

• @-mentions of the team name in organizations
• Review requests of the team in pull requests
• Adding the team to a project board
• Team sync if you use GitHub Enterprise Cloud with personal accounts
• CODEOWNER status
• Secret teams
• Nested teams
• Team maintainers

There are limits on enterprise teams. You can create up to 100 teams for a single enterprise and add up to 500 users to each team. Each team can be assigned to a maximum of 1,000 organizations.

For more information about the capabilities of organization teams, see Organization のチームについて.

Next steps

If your needs are covered by enterprise teams, create a team. See Enterprise チームの作成.

If you need to create an organization team, an organization owner must do this from the organization settings. See Organization のチームの作成.