{"meta":{"title":"Teams in an enterprise","intro":"Simplify administration of user access, licensing, and communication with teams.","product":"Enterprise administrators","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/admin","title":"Enterprise administrators"},{"href":"/en/enterprise-cloud@latest/admin/concepts","title":"Concepts"},{"href":"/en/enterprise-cloud@latest/admin/concepts/enterprise-fundamentals","title":"Fundamentals"},{"href":"/en/enterprise-cloud@latest/admin/concepts/enterprise-fundamentals/teams-in-an-enterprise","title":"Teams"}],"documentType":"article"},"body":"# Teams in an enterprise\n\nSimplify administration of user access, licensing, and communication with teams.\n\n## What are teams?\n\nTeams 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.\n\n**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.\n\n**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.\n\n## Can I manage teams from an identity provider?\n\nIf 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.\n\nThe capabilities of this feature depend on whether you use Enterprise Managed Users or personal accounts.\n\n### Enterprise Managed Users\n\nYou 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 [Managing team memberships with identity provider groups](/en/enterprise-cloud@latest/admin/managing-iam/provisioning-user-accounts-with-scim/managing-team-memberships-with-identity-provider-groups).\n\nThis feature is available with both enterprise and organization teams.\n\n### Personal accounts\n\nTeam 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 [Managing team synchronization for organizations in your enterprise](/en/enterprise-cloud@latest/admin/managing-iam/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise).\n\nTeam sync with personal accounts is only available with organization teams, and you must use Entra ID or Okta as an IdP.\n\n## What kind of team should I use?\n\nTo 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.\n\nYou may need to create organization teams if the functionality you need is not covered by enterprise teams. The limitations listed below reflect the current capabilities of enterprise teams and may change over time.\n\n## What can enterprise teams do?\n\nEnterprise teams can:\n\n* Receive **Copilot Business licenses** directly from the enterprise.\n* Be granted access to specific Copilot models (opt-in preview).\n* Be assigned **predefined and custom enterprise roles**, giving members access to enterprise settings.\n* Be **added to organizations**, where organization administrators can grant the team additional access and permissions.\n* Receive **bypass access** on rulesets.\n* Be mentioned, assigned, or requested for review in **issues and pull requests**.\n\nTo @-mention an enterprise team, or request a review from the team, use the team's slug in the format `@/ent:TEAM-SLUG`. GitHub generates the slug from the team's name and adds the `ent:` prefix, so an enterprise team named `Platform SRE` has the slug `ent:platform-sre`.\n\nTo mention the team from an organization it is assigned to, such as `octo-org`, use `@octo-org/ent:platform-sre`. You can mention an enterprise team from any organization the team is assigned to.\n\nHowever, unlike organization teams, enterprise teams currently do **not** support:\n\n* Adding the team to a project board\n* Team sync if you use GitHub Enterprise Cloud with personal accounts\n* CODEOWNER status\n* Secret teams\n* Nested teams\n* Team maintainers\n\nThere are **limits on enterprise teams**. You can create up to 2,500 teams for a single enterprise and add up to 5,000 users to each team. Each team can be assigned to a maximum of 1,000 organizations.\n\nFor more information about the capabilities of organization teams, see [About organization teams](/en/enterprise-cloud@latest/organizations/organizing-members-into-teams/about-teams)."}