Question

An enterprise owner on GitHub Enterprise Cloud (without Enterprise Managed Users) notices that a contractor was added directly to a single private repository in the Acme-Web organization, but the contractor is NOT a member of the organization. Leadership wants to ensure this contractor cannot see any other private repositories in the organization and cannot be counted against internal team-based base permissions. Which statement correctly describes the contractor's status and how their access is governed?

Accepted Answer

The contractor is an outside collaborator, so the organization's base permission setting does not grant them any access; they can only access repositories to which they are explicitly added.

Answer

The contractor is automatically an organization member because they were granted repository access, so the base permission setting applies and must be set to 'None' to restrict them.

Answer

The contractor is a billable enterprise team member, so they inherit read access to all internal repositories in the organization by default.

Answer

The contractor's access is controlled by SCIM provisioning attributes, so their repository access can only be limited by adjusting the identity provider group mapping.