Update project definitions for Pages Access
What does this MR do?
Update the definitions for Pages Access for public and private projects. The current definitions seems to be swapped.
This MR swaps the definitions, and removes the everyone with access definition from private projects, since members need to be explicitly added.
Screenshots (strongly suggested)
If your project is private:
- Only project members: Only project members are able to browse the website.
- Everyone: Everyone, both logged into and logged out of GitLab, is able to browse the website, no matter their project >membership.
If your project is public:
- Only project members: Only project members are able to browse the website.
- Everyone with access: Everyone, both logged into and logged out of GitLab, is able to browse the website, no matter their >project membership.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team