|
| 1 | +--- |
| 2 | +title: About teams in an enterprise |
| 3 | +intro: 'Learn how teams simplify administration of user access, licensing, and communication.' |
| 4 | +versions: |
| 5 | + ghec: '*' |
| 6 | +shortTitle: About teams |
| 7 | +type: overview |
| 8 | +topics: |
| 9 | + - Enterprise |
| 10 | + - Fundamentals |
| 11 | +--- |
| 12 | + |
| 13 | +## What are teams? |
| 14 | + |
| 15 | +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 {% data variables.product.prodname_copilot_short %} team for users who receive {% data variables.product.prodname_copilot_short %} licenses. |
| 16 | + |
| 17 | +Administrators can create teams in an enterprise account or in organizations within an enterprise. |
| 18 | + |
| 19 | +* **Enterprise teams** are managed by enterprise owners and can include users from across the enterprise and its organizations. Currently, enterprise teams are used to manage {% data variables.product.prodname_copilot %} licenses for directly assigned users. {% data variables.product.company_short %} plans to expand the capabilities in the near future to include organization and role assignment. |
| 20 | +* **Organization teams** are managed by organization administrators and can only include members of a single organization. Organization administrators can grant teams access to organization repositories, and organization members can mention teams in issues and discussions or add them as reviewers on pull requests. |
| 21 | + |
| 22 | +## Can I manage teams from an identity provider? |
| 23 | + |
| 24 | +If you have integrated {% data variables.product.github %} with an identity provider (IdP), you can link teams on {% data variables.product.github %} with groups in your IdP. When membership of the IdP group changes, the change is reflected in the {% data variables.product.github %} team, allowing you to centralize access management. |
| 25 | + |
| 26 | +The capabilities of this feature depend on whether you use {% data variables.product.prodname_emus %} or personal accounts. |
| 27 | + |
| 28 | +### {% data variables.product.prodname_emus %} |
| 29 | + |
| 30 | +You can make changes to IdP groups to manage repository access, add or remove users from organizations, or grant or remove {% data variables.product.prodname_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 [AUTOTITLE](/admin/managing-iam/provisioning-user-accounts-with-scim/managing-team-memberships-with-identity-provider-groups#about-team-management-with-enterprise-managed-users). |
| 31 | + |
| 32 | +This feature is available with both enterprise and organization teams. |
| 33 | + |
| 34 | +### Personal accounts |
| 35 | + |
| 36 | +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 [AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise). |
| 37 | + |
| 38 | +Team sync with personal accounts is only available with organization teams, and you must use Entra ID or Okta as an IdP. |
| 39 | + |
| 40 | +## What kind of team should I use? |
| 41 | + |
| 42 | +To simplify administration at scale, {% data variables.product.company_short %} recommends using enterprise teams wherever possible. However, you may need to create organization teams if the functionality you need is not covered by enterprise teams. {% data variables.product.company_short %} plans to address some of these limitations in the near future. |
| 43 | + |
| 44 | +Unlike organization teams, enterprise teams currently do **not** support: |
| 45 | + |
| 46 | +* Repository or organization access |
| 47 | +* `@-mentions` of the team name in organizations |
| 48 | +* Team sync if you use {% data variables.product.prodname_ghe_cloud %} with personal accounts |
| 49 | +* CODEOWNER status |
| 50 | +* Secret teams |
| 51 | +* Nested teams |
| 52 | +* Team maintainers |
| 53 | + |
| 54 | +In addition, enterprise teams are currently limited to 50 teams for a single enterprise and 500 users to each team. |
| 55 | + |
| 56 | +For more information about the capabilities of organization teams, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams). |
0 commit comments