Organizing members into teams

Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions.

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

People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also add non-members to a team and the organization.

You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.

Team maintainers and organization owners can set a profile picture for a team, which is displayed on the team's page.

You can decrease noise for your team by limiting notifications when your team is requested to review a pull request.

Team maintainers and organization owners can edit the name and description of a team.

Team maintainers and organization owners can determine whether a team is visible or secret.

You can synchronize a GitHub Enterprise Server team with a supported identity provider (IdP) group to automatically add and remove team members.

Team maintainers and organization owners can nest a team under a parent team, or change or remove a nested team's parent.

If you have maintainer permissions in a team, you can request to nest an existing team under your team in your organization’s hierarchy.

If you have maintainer permissions in a team, you can request to nest your team under a parent team in your organization's hierarchy.

People with owner or team maintainer permissions can remove team members from a team. This may be necessary if a person no longer needs access to a repository the team grants, or if a person is no longer focused on a team's projects.

Organization owners can choose to disable or enable team discussions across the organization.

Organization owners can delete teams at any time from the team's settings page.