Skip to main content

This version of GitHub Enterprise Server will be discontinued on 2024-06-29. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

Creating a team

You can create independent or nested teams to manage repository permissions and mentions for groups of people.

Who can use this feature?

Organization owners can create teams and can control whether all organization members can also create teams. For more information, see "Setting team creation permissions in your organization."

Creating a team

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

  2. Click the name of your organization.

  3. Under your organization name, click Teams.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with the people icon and "Teams," is outlined in dark orange.

  4. At the top of the page, click New team.

  5. Under "Create new team", type the name for your new team.

  6. Optionally, in the "Description" field, type a description of the team.

  7. Optionally, if you're creating a child team, under "Parent team", select the Select a parent team dropdown menu and click a parent team. For more information about child teams, see "About teams."

  8. Under "Team visibility", select a visibility for the team.

  9. Under "Team notifications", select Enabled or Disabled.

    Note: This setting only applies to @mentions of the team name. This setting does not affect notifications for reviews requested from the team.

  10. Click Create team.

  11. Optionally, give the team access to organization repositories. For more information, see "Managing team access to an organization repository."

Creating teams with LDAP Sync enabled

Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's Distinguished Name (DN) in the LDAP group field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within your GitHub Enterprise Server instance. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "Using LDAP."

You must be a site admin and an organization owner to create a team with LDAP sync enabled.

As part of its optimization configuration, LDAP Sync will not transfer your nested team structure. To create child and parent team relationships, you must manually recreate the nested team structure and sync it with the corresponding LDAP group. For more information, see "Creating a team"

Notes:

  • LDAP Sync only manages the team's member list. You must manage the team's repositories and permissions from within GitHub Enterprise Server.
  • If an LDAP group mapping to a DN is removed, such as if the LDAP group is deleted, then every member is removed from the synced GitHub Enterprise Server team. To fix this, map the team to a new DN, add the team members back, and manually sync the mapping.
  • When LDAP Sync is enabled, if a person is removed from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.
  1. Ensure that LDAP Sync is enabled.

  2. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

  3. Click the name of your organization.

  4. Under your organization name, click Teams.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with the people icon and "Teams," is outlined in dark orange.

  5. At the top of the page, click New team.

  6. Under "Create new team", type the name for your new team.

  7. Under "LDAP group", search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. GitHub Enterprise Server will search for and autocomplete any matches.

  8. Optionally, in the "Description" field, type a description of the team.

  9. Under "Team visibility", select a visibility for the team.

  10. Optionally, if you're creating a child team, under "Parent team", select the Select a parent team dropdown menu and click a parent team. For more information about child teams, see "About teams."

  11. Click Create team.