diff options
Diffstat (limited to 'doc/public_access/public_access.md')
| -rw-r--r-- | doc/public_access/public_access.md | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/public_access/public_access.md b/doc/public_access/public_access.md index 1b4e1e64562..e0b07abd4e9 100644 --- a/doc/public_access/public_access.md +++ b/doc/public_access/public_access.md @@ -1,13 +1,13 @@ --- -stage: none -group: unassigned +stage: Manage +group: Workspace info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: reference --- -# Project and group visibility +# Project and group visibility **(FREE)** -GitLab allows [Owners](../user/permissions.md) to set a project's or group's visibility as: +GitLab allows users with the Owner [role](../user/permissions.md) to set a project's or group's visibility as: - **Public** - **Internal** @@ -24,7 +24,7 @@ Public projects can be cloned **without any** authentication over HTTPS. They are listed in the public access directory (`/public`) for all users. -**Any signed-in user** has the [Guest role](../user/permissions.md) on the repository. +**Any signed-in user** has the Guest [role](../user/permissions.md) on the repository. NOTE: By default, `/public` is visible to unauthenticated users. However, if the @@ -39,7 +39,7 @@ Internal projects can be cloned by any signed-in user except They are also listed in the public access directory (`/public`), but only for signed-in users. Any signed-in users except [external users](../user/permissions.md#external-users) have the -[Guest role](../user/permissions.md) on the repository. +Guest [role](../user/permissions.md) on the repository. NOTE: From July 2019, the `Internal` visibility setting is disabled for new projects, groups, @@ -57,7 +57,7 @@ They appear in the public access directory (`/public`) for project members only. Prerequisite: -- You must have the Owner role for a project. +- You must have the Owner [role](../user/permissions.md) for a project. 1. On the top bar, select **Menu > Projects** and find your project. 1. On the left sidebar, select **Settings > General**. @@ -69,7 +69,7 @@ Prerequisite: Prerequisite: -- You must have the Owner role for a group. +- You must have the Owner [role](../user/permissions.md) for a group. 1. On the top bar, select **Menu > Groups** and find your project. 1. On the left sidebar, select **Settings > General**. @@ -77,11 +77,11 @@ Prerequisite: 1. Under **Visibility level** select either **Private**, **Internal**, or **Public**. 1. Select **Save changes**. -## Restrict use of public or internal projects +## Restrict use of public or internal projects **(FREE SELF)** You can restrict the use of visibility levels for users when they create a project or a snippet. This is useful to prevent users from publicly exposing their repositories by accident. The -restricted visibility settings do not apply to admin users. +restricted visibility settings do not apply to administrators. For details, see [Restricted visibility levels](../user/admin_area/settings/visibility_and_access_controls.md#restrict-visibility-levels). |