Inviting an external collaborator to a project? Easy right...? Right....?

[BlauweStadTechnologieen]

🏷️ Discussion Type

Question

Body

Can somebody explain to me why, despite inviting an external collaborator to a project in a private repo, does the invitee not see the project with which are are invited to, despite accepting the invite?

Why does GitHub make it so difficult? What is so difficult about simply allowing the invitee to see whatever they're being invited to collaborate on?

Why make something easy when you can make it impossible?

[lucaasporto]

The issue is that GitHub manages access to Projects separately. Being an external collaborator on a repository doesn't automatically mean you have access to the Project itself. The Project owner/admin may need to grant you access to the Project under Settings → Manage access.

You can find more details in the official GitHub documentation here: GitHub Docs — Managing access to your projects

[BlauweStadTechnologieen]

The owner has granted access to the project WITHIN the private repository as well.

Can an external collaborator have access to a private project within a private repo, but not have access to the full private repo itself?

Many thanks

[lucaasporto]

An external collaborator can be granted access to the project board without having access to the private repository itself. However, because project permissions and repository permissions are separate, they will not be able to see any issues or pull requests that come from that private repository.

This is explicitly stated in the "Granting a collaborator access to your project" section:

[lucaasporto]

@BlauweStadTechnologieen Did this help you? If so, please mark the topic as answered. Thanks!