> 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.

Finally.

> Membership inheritance from parent to child teams isn't automatic. If you're a member of Engineering and someone creates a child team called Security, team members of Engineering aren't automatically direct team members of Security.

Ok that was worded weirdly, but it makes sense. I think the wording of "parent" and "child" teams is confusing, "super" and "sub" teams is much clearer, and it makes perfect sense that when you create a subteam it starts empty, the opposite would be completely broken since the entire point of subteams would be to increase access rights.

One thing they did not touch upon though: can you be a member of a team and one of its subteams? (that would be somewhat annoying).