GitLab Pages access control

You can enable Pages access control on your project if your administrator has enabled the access control feature on your GitLab instance. When enabled, only authenticated members of your project (at least Guest) can access your website, by default:

For a demonstration, see Pages access controls.

1. On the left sidebar, select Search or go to and find your project.

2. Select Settings > General.

3. Expand Visibility, project features, permissions.

4. Toggle the Pages button to enable the access control. If you don’t see the toggle button, that means it isn’t enabled. Ask your administrator to enable it.

5. The Pages access control dropdown list allows you to set who can view pages hosted with GitLab Pages, depending on your project’s visibility:

   • 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 internal:
     • Only project members: Only project members are able to browse the website.
     • Everyone with access: Everyone logged into GitLab is able to browse the website, no matter their project membership.
     • 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.

6. Select Save changes. Your changes may not take effect immediately. GitLab Pages uses a caching mechanism for efficiency. Your changes may not take effect until that cache is invalidated, which usually takes less than a minute.

The next time someone tries to access your website and the access control is enabled, they’re presented with a page to sign in to GitLab and verify they can access the website.

Restrict Pages access to project members for the group and its subgroups

You can configure a setting for the group to restrict Pages access to only project members. When enabled, all projects in the group and its subgroups become visible only to members.

Prerequisites

• Public access to Pages must not be disabled at the instance level.
• You must have the Owner role for the group.

To do this:

1. On the left sidebar, select Search or go to and find your group.
2. Select Settings > General.
3. Expand Permissions and group features.
4. Under Pages access control, select Restrict access to only project members on all group projects.
5. Select Save changes.

GitLab Pages uses a cache for efficiency. Changes to access settings typically take effect within one minute when the cache updates.

Terminating a Pages session

To sign out of your GitLab Pages website, revoke the application access token for GitLab Pages:

1. On the left sidebar, select your avatar.
2. Select Edit profile.
3. Select Applications.
4. In the Authorized applications section, find the GitLab Pages entry, and select Revoke.