Enable external users to access internal-visibility GitLab Pages deployments without direct invitations
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
- Currently the permissions for accessing a GitLab Pages deployment is tied to the deploying projects visibility settings [GitLab Pages access control documentation]
- For the
internalvisibility level there is the option ofEveryone with access, with the explanation: "Everyone with access: Everyone logged into GitLab is able to browse the website, no matter their project membership."- This applies to all non-external users, however External users can only access projects they are directly invited to (and so by default cannot access
internalprojects that they are not invited to)
- This applies to all non-external users, however External users can only access projects they are directly invited to (and so by default cannot access
-
This customer has requested this functionality as they have over a thousand external users that they'd like to provide access to an
internalGitLab Pages deployment to (without the overhead of inviting the users to the project)
Potential Approaches
- Enable access for External users to
internalprojects - Add a project-level setting (within
internalprojects) to enable access for external users - Add an instance-level setting (or whitelist) to enable external users to access
internalvisibility projects/Pages deployments
- I understand there are security implications to this suggested change, so I'm not in favour of option
1.however I can see the utility of2.or3..
Edited by 🤖 GitLab Bot 🤖