Skip to main content

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.

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.

Please see the screenshot below for an example:

Screen_Shot_2020-08-18_at_10_20_11_AM.png

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.

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

Did this answer your question?