About organization teams - GitHub Docs Skip to main content GitHub Docs Version: Free, Pro, & Team Search or ask Copilot Search or ask Copilot Select language: current language is English Search or ask Copilot Search or ask Copilot Open menu Collapse sidebar Expand sidebar Scroll breadcrumbs left * Home * Organizations * Organize members into teams * About organization teams Scroll breadcrumbs right Organizations * * * Collaborate with groups * About organizations * Organization dashboard * Best practices * Create new organization * Access organization settings * Customize organization profile * Organization news feed * GitHub Actions metrics * Manage membership * Invite users to join * Cancel or edit invitation * Remove a member * Reinstate a member * Export member information * Create accounts for people * Manage organization roles * Roles in an organization * Use organization roles * Predefined roles permissions * Maintain ownership continuity * Add a billing manager * Remove billing manager * Security manager role * Managing moderators * Manage repository access * Manage repository roles * Repository roles * Set base permissions * View people with access * Manage individual access * Manage team access * Manage outside collaborators * Add outside collaborator * Cancel collaborator invitation * Remove collaborator * Convert member to collaborator * Convert collaborator to member * Reinstate collaborator * Organize members into teams * About organization teams * Creating an organization team * Add members to a team * Team maintainers * Team profile picture * Code review settings * Renaming a team * Changing team visibility * Configuring team notifications * Move a team * Add a child team * Add or change parent team * Remove members * Scheduled reminders * Deleting a team * Manage programmatic access * About programmatic access * GitHub App managers * Review installed GitHub Apps * Set a token policy * Manage token requests * Review token access * Limit app requests and installations * Credential types reference * Manage OAuth access * OAuth app restrictions * Restrict OAuth apps * Unrestrict OAuth apps * Approve OAuth app access * Deny OAuth app access * Manage organization settings * Verify or approve a domain * Renaming an organization * Transfer ownership * Restrict repository creation * Set repo management policy * Set visibility changes policy * Manage forking policy * Manage pull request reviews * Disable or limit actions * Actions policies * About Actions policies * Workflow execution protections * About private networking * About Azure private networking * Configuring private networking * Troubleshooting Azure private networking * Configure retention period * Allow issue deletion * Allow branch renames * Organization discussions * Manage repository discussions * Manage the commit signoff policy * Restrict team creation * Manage scheduled reminders * Manage default branch name * Manage default labels * Manage display of member names * Manage sponsorship updates * Manage Pages site publication * Manage commit comments * Archive an organization * Delete organization * Convert organization to user * Upgrade to Corporate ToS * Disable projects * Manage projects base permissions * Project visibility permissions * Create rulesets * Manage rulesets * Repository custom properties * Organization security * Manage 2FA * View 2FA usage * Prepare to require 2FA * Require 2FA * Manage bots & service accounts * Manage security settings * Manage security & analysis * Review audit log * IP addresses in audit log * Audit log events * Access compliance reports * Migrate to improved permissions * Convert Owners team * Convert admin team * Migrate admin team About organization teams Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions. Copy as Markdown In this article * About teams * Team visibility * Team pages * Nested teams * Preparing to nest teams in your organization * Further reading About teams You can use teams to manage access for people in an organization, and for sending notifications. Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Teams can only be made up of members of your organization, outside collaborators are unable to be on a team. Tip If you use an enterprise account, you can also create teams at the enterprise level. For more information, see Teams in an enterprise . Organization members can send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file. For more information, see: * Managing team access to an organization repository * Basic writing and formatting syntax * About code owners Organizations that use GitHub Enterprise Cloud can use team synchronization to automatically add and remove organization members to teams through an identity provider. For more information, see Synchronizing a team with an identity provider group in the GitHub Enterprise Cloud documentation. Team visibility Teams can be visible or secret: * Visible teams can be viewed and @mentioned by every organization member. * Secret teams are only visible to the people on the team and organization owners. They're great for hiding the members of teams that work with external partners or clients. However, if a team member or organization owner mentions a secret team, the team name is visible in the mention text. Secret teams cannot be nested under parent teams or have child teams. People who are not members of the organization cannot view any teams. You can view all the teams you belong to on your personal dashboard. For more information, see Quickstart for your personal dashboard . Team pages Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page. Note Team Discussions are retired. You can read more about this on the GitHub Blog . You can use GitHub Discussions to create organization-level discussions. For more information about GitHub Discussions, see GitHub Discussions documentation . Nested teams You can reflect your group or company's hierarchy within your GitHub organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. Each nested team functions as a distinct entity with its own unique URL and directory within your organization. Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people. For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification. When mentioning a team, you do not need to include the full hierarchical path. Even though a team is nested, it retains a flat handle for mentions. To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team. You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, Moving a team in your organization's hierarchy . Preparing to nest teams in your organization If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization. At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories. * Remove all members from existing teams * Audit and adjust each team's repository access permissions and give each team a parent * Create any new teams you'd like to, choose a parent for each new team, and give them repository access * Add people directly to teams Further reading * Creating an organization team * Adding organization members to a team Back to top Help and support Was this Doc helpful? Yes No Help us make GitHub Docs great! All Docs are open source. See something that's wrong or unclear? Submit a pull request. Make a contribution Still need help? Ask the GitHub community Contact support Expert services Blog GitHub Inc. © 2026 Terms Privacy Status Pricing