summaryrefslogtreecommitdiff
path: root/doc/user/project/pages/introduction.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/pages/introduction.md')
-rw-r--r--doc/user/project/pages/introduction.md27
1 files changed, 13 insertions, 14 deletions
diff --git a/doc/user/project/pages/introduction.md b/doc/user/project/pages/introduction.md
index f68cf25c09a..9f9b64ec20d 100644
--- a/doc/user/project/pages/introduction.md
+++ b/doc/user/project/pages/introduction.md
@@ -446,35 +446,34 @@ See also: [GitLab Pages from A to Z: Part 1 - Static sites and GitLab Pages doma
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/33422) in GitLab 11.5.
NOTE: **Note:**
-GitLab Pages access control is not activated on GitLab.com. Follow this
-[issue]() for more information.
+GitLab Pages access control is not activated on GitLab.com.
You can enable Pages access control on your project, so that only
[members of your project](../../permissions.md#project-members-permissions)
-at least Guest) can access your website:
+(at least Guest) can access your website:
-1. Navigate to your project's **Settings > General > Permissions**.
-1. Toggle the "Pages" button to enable the access control.
+1. Navigate to your project's **Settings > General > Permissions**.
+1. Toggle the **Pages** button to enable the access control.
NOTE: **Note:**
If you don't see the toggle button, that means that it's not enabled.
Ask your administrator to [enable it](../../../administration/pages/index.md#access-control).
-1. Depending on the visibility of your project, you can also choose who gets to
- have access:
+1. The Pages access control dropdown allows you to set who can view pages hosted
+ with GitLab Pages, depending on your project's visibility:
- - If your project is public:
- - **Everyone with access**: Everyone inside and outside of GitLab will be able to browse the website.
+ - If your project is private:
- **Only project members**: Only project members will be able to browse the website.
+ - **Everyone**: Everyone, both logged into and logged out of GitLab, will be able to browse the website, no matter their project membership.
- If your project is internal:
- - **Everyone with access**: Everyone inside GitLab will be able to browse the website.
- **Only project members**: Only project members will be able to browse the website.
- - **Everyone**: Everyone inside and outside of GitLab will be able to browse the website.
- - If your project is private:
- - **Everyone**: Everyone inside and outside of GitLab will be able to browse the website.
+ - **Everyone with access**: Everyone logged into GitLab will be able to browse the website, no matter their project membership.
+ - **Everyone**: Everyone, both logged into and logged out of GitLab, will be able to browse the website, no matter their project membership.
+ - If your project is public:
- **Only project members**: Only project members will be able to browse the website.
+ - **Everyone with access**: Everyone, both logged into and logged out of GitLab, will be able to browse the website, no matter their project membership.
-1. Click **Save changes**.
+1. Click **Save changes**.
---