Nested teams add depth to your team structure

GitHub now supports multiple levels of nested teams within an organization, allowing for a clearer and more manageable hierarchy that reflects a company's structure. This system enables child teams to inherit access permissions from their parent teams, ensuring that repository permissions and @mention functionalities work seamlessly from the top of the hierarchy down to the bottom. For instance, if the Engineering team is granted write access to a repository, all sub-teams, such as Application Engineering and Identity, will also receive that access. However, while permissions and @mentions are inherited, membership is not; members of a parent team like Engineering do not automatically become members of a newly created child team like Security. This nested structure aims to streamline permissions management and communication, and further details can be found in the official documentation.