GH-100 · Domain 1: Manage GitHub identities and access · 19% of the exam
Task 1.2: Manage access and permissions
Organization and repository roles, custom roles and base permissions, teams and enterprise teams, reviewing who can reach what, and the settings, policies and rulesets that shape access.
Study it
Organization and repository roles, custom roles, teams and enterprise teams
Lesson coming
Central policies that cap what member organizations may allow
Reviewing access, and the settings and rulesets that shape it
Lesson coming
Sample questions
Try each one before opening the answer. Every option is explained, with the GitHub documentation page that proves it.
Question 1 · choose 1
An organization's base permission is Write. Its owner creates a custom repository role, Webhook admin, that inherits Read and adds Manage webhooks, and assigns it to the integrations team on the billing repository. The team members, all organization members, can still push to billing. What explains this, and what fixes it while keeping the custom role?
AThe inherited role is the problem; recreate the custom role so that it inherits Triage instead of Read
BManage webhooks needs a Write base role, so GitHub raised the role; remove that permission
CRoles are additive, so base Write still applies; lower the base permission and grant Write to the teams that need it
DTeam roles override base permissions; assign the custom role to each member directly instead
Show the answer and why
AThe inherited role is the problem; recreate the custom role so that it inherits Triage instead of Read
Incorrect
Roles are additive, so base Write would still apply alongside any inherited role.
BManage webhooks needs a Write base role, so GitHub raised the role; remove that permission
Incorrect
Only "Push commits to protected branches" requires a Write base role; Manage webhooks doesn't.
CRoles are additive, so base Write still applies; lower the base permission and grant Write to the teams that need it
Correct
Members get the sum of all their grants, so base Write adds push access to the custom role.
DTeam roles override base permissions; assign the custom role to each member directly instead
Incorrect
Direct, team and base grants are all added together; none of them overrides another.
A custom repository role starts from an inherited role and adds permissions. Roles and permissions are additive: a person given access through several avenues, such as team membership and the organization's base permission, has the sum of all the grants. With base Write, members holding a Read-based custom role still have write access, so the base permission must be lowered for the custom role to limit them.
An enterprise's 30 site reliability engineers belong to six of its organizations, five engineers in each. The enterprise owners want to grant all 30 a Copilot Business license in one place, at the enterprise level. The engineers must also be the code owners of the deploy/ directory in the repositories of all six organizations, so that their review is required there. What should the owners set up?
AOne enterprise team with all 30 engineers, given the licenses and named as the code owner of deploy/ in every repository
BAn enterprise team for the licenses, plus a team of each organization's engineers in that organization, named as the code owner there
CAn enterprise team for the licenses, plus one team of all 30 engineers in the first organization, named as the code owner in every repository
DOne enterprise team for the licenses, added to all six organizations and then named as the code owner of deploy/ there
Show the answer and why
AOne enterprise team with all 30 engineers, given the licenses and named as the code owner of deploy/ in every repository
Incorrect
Enterprise teams aren't supported as code owners, so the CODEOWNERS entry assigns no one.
BAn enterprise team for the licenses, plus a team of each organization's engineers in that organization, named as the code owner there
Correct
The enterprise team takes the licenses across organizations, and organization teams can be code owners in their own organization.
CAn enterprise team for the licenses, plus one team of all 30 engineers in the first organization, named as the code owner in every repository
Incorrect
An organization team can include only members of its own organization.
DOne enterprise team for the licenses, added to all six organizations and then named as the code owner of deploy/ there
Incorrect
Adding an enterprise team to organizations doesn't give it code owner status; only organization teams can be code owners.
Enterprise teams can include users from across the enterprise and receive Copilot Business licenses directly from the enterprise, but they don't support CODEOWNER status: only organization teams can be code owners. Organization teams can include only members of a single organization, so code ownership in six organizations needs a team in each of them, while one enterprise team carries the licenses.
For a compliance review, an auditor asks for a file that lists everyone who can currently access the payroll repository, whether through teams, direct grants or as outside collaborators. The organization uses GitHub Enterprise Cloud. Which source should an organization owner use?
AThe enterprise's membership information report, downloaded as CSV
BThe enterprise's credential inventory, exported from Authentication security
CAn audit log export filtered to the payroll repository
DThe People list under the repository's Insights, exported as CSV
Show the answer and why
AThe enterprise's membership information report, downloaded as CSV
Incorrect
That report covers people's membership, roles and 2FA, not who can access a particular repository.
BThe enterprise's credential inventory, exported from Authentication security
Incorrect
The inventory lists credentials that can access the enterprise, not people's access to one repository.
CAn audit log export filtered to the payroll repository
Incorrect
The audit log records events; it isn't a list of the people who have access now.
DThe People list under the repository's Insights, exported as CSV
Correct
Organization owners can export the list of people with access to a repository for compliance checks.
On GitHub Enterprise Cloud, organization owners can view and export a list of people with access to a repository, from Insights and then People, to help off-board people and gather compliance data. The enterprise membership report and the credential inventory answer other questions, and the audit log records events rather than current access.
After a team lead deleted a repository by mistake, an organization owner wants only organization owners to be able to delete or transfer repositories. Repository administrators must keep their admin access for everything else. Which change achieves this?
AAn organization ruleset for all repositories with the Restrict deletions rule
BLower the organization's base permission to Read for all members
CDeselect "Allow members to delete or transfer repositories" in member privileges
DSet the organization's forking policy so private and internal repositories can't be forked
Show the answer and why
AAn organization ruleset for all repositories with the Restrict deletions rule
Incorrect
Ruleset rules control branches and tags; Restrict deletions stops deleting matching refs, not the repository.
BLower the organization's base permission to Read for all members
Incorrect
Base permissions add to other grants; they don't take admin access away from repository administrators.
CDeselect "Allow members to delete or transfer repositories" in member privileges
Correct
With that setting off, only organization owners can delete or transfer repositories.
DSet the organization's forking policy so private and internal repositories can't be forked
Incorrect
The forking policy controls who can fork repositories, not who can delete or transfer them.
Organization owners can let members with admin permissions delete or transfer repositories, or limit both actions to organization owners in the organization's member privileges. Rulesets control how people interact with branches and tags, and base permissions are added to other grants rather than removing admin access.
An organization owner converts a consultant, who was a member on two teams, to an outside collaborator. The consultant had also been added directly to one repository. Which repositories can the consultant still access?
ANone, because converting removes all of the person's repository access
BOnly the repository the consultant was added to directly
CEvery repository that the organization's base permission covers
DThe directly added repository and the repositories of the two former teams
Show the answer and why
ANone, because converting removes all of the person's repository access
Incorrect
Converted members keep access to repositories they had directly and through their former teams.
BOnly the repository the consultant was added to directly
Incorrect
Access that came through the former team memberships is kept as well.
CEvery repository that the organization's base permission covers
Incorrect
Outside collaborators aren't members, so base permissions don't apply to them.
DThe directly added repository and the repositories of the two former teams
Correct
Converted members keep access to repositories they were added to directly and through former teams.
After a member is converted to an outside collaborator, they are no longer an explicit member of the organization and are removed from all teams. They retain access to repositories they were directly added to, as well as those they had through their former team memberships.
An enterprise team named Platform SRE is assigned to the octo-org organization. A developer in octo-org wants to request a review from that team on a pull request. Which handle should she use?
A@octo-org/ent:platform-sre
B@octo-org/platform-sre
C@octo-enterprise/ent:platform-sre
D@platform-sre
Show the answer and why
A@octo-org/ent:platform-sre
Correct
From an assigned organization, an enterprise team is mentioned as the organization plus its ent: slug.
B@octo-org/platform-sre
Incorrect
That form names an organization team; enterprise team slugs carry the ent: prefix.
C@octo-enterprise/ent:platform-sre
Incorrect
From an assigned organization, the organization name, not the enterprise, comes before the slug.
D@platform-sre
Incorrect
A bare name doesn't identify a team; teams are named with a slug.
GitHub generates an enterprise team's slug from its name with the ent: prefix, so Platform SRE becomes ent:platform-sre. From an organization the team is assigned to, such as octo-org, you mention it as @octo-org/ent:platform-sre, for example to request a review.
An enterprise owner sets the repository creation policy so that members can't create repositories in any of the enterprise's organizations. Who can still create repositories in those organizations?
ARepository administrators in each organization
BOutside collaborators with admin access to a repository
COrganization owners
DMembers who hold the Maintain role on a repository
Show the answer and why
ARepository administrators in each organization
Incorrect
With the policy set, members, including repository admins, can't create repositories.
BOutside collaborators with admin access to a repository
Incorrect
Outside collaborators can never create repositories in the organization.
COrganization owners
Correct
Organization owners can always create any type of repository.
DMembers who hold the Maintain role on a repository
Incorrect
Repository roles don't grant the right to create repositories when the policy blocks members.
Enterprise owners can let members create repositories, of selected types, or prevent them from creating any. Organization owners can always create any type of repository, and outside collaborators can never create one.