Using and sharing context with GitHub Nested Teams

Nested teams within GitHub do not automatically inherit a parent team's context permissions. If a parent team is selected as a security group for a context, child teams are not automatically granted access.

In order to grant a GitHub child team access to context, you will need to add the team as a security group for the context. If a child team is not listed as a security group you will get an "Unauthorized" error when triggering a build in CircleCI's UI (example below).





For more information on contexts please refer to our official documentation:

Was this article helpful?
2 out of 7 found this helpful



Article is closed for comments.