diff options
author | Marcel Amirault <ravlen@gmail.com> | 2019-05-24 08:03:22 +0000 |
---|---|---|
committer | Marcel Amirault <ravlen@gmail.com> | 2019-06-10 01:10:17 +0000 |
commit | 20c66d6e29df21df437f3f11afd0dd5c1b1230fe (patch) | |
tree | 085149020a13d152b2b95a5ad0b49e3371f0a043 /doc/public_access | |
parent | 72611cbc3a81647cc7f93cd8a84ae3b9f37ec8c7 (diff) | |
download | gitlab-ce-20c66d6e29df21df437f3f11afd0dd5c1b1230fe.tar.gz |
SSOT edits to docs that are alone in root directories
Diffstat (limited to 'doc/public_access')
-rw-r--r-- | doc/public_access/public_access.md | 43 |
1 files changed, 27 insertions, 16 deletions
diff --git a/doc/public_access/public_access.md b/doc/public_access/public_access.md index 8601551e3bd..b2bfafe8ac9 100644 --- a/doc/public_access/public_access.md +++ b/doc/public_access/public_access.md @@ -1,13 +1,12 @@ -# Public access - -GitLab allows [Owners](../user/permissions.md) to change a projects' visibility in order to be accessed -**publicly** or **internally**. +--- +type: reference +--- -Projects with either of these visibility levels will be listed in the -public access directory (`/public` under your GitLab instance). -Here is the [GitLab.com example](https://gitlab.com/public). +# Public access -Internal projects will only be available to authenticated users. +GitLab allows [Owners](../user/permissions.md) to set a projects' visibility as **public**, **internal** +or **private**. These visibility levels will affect who will be able to see the project in in the +public access directory (`/public` under your GitLab instance), like at [https://gitlab.com/public](). ## Visibility of projects @@ -15,26 +14,26 @@ Internal projects will only be available to authenticated users. Public projects can be cloned **without any** authentication. -They will also be listed on the public access directory (`/public`). +They will be listed in the public access directory (`/public`) for all users. -**Any logged in user** will have [Guest](../user/permissions.md) -permissions on the repository. +**Any logged in user** will have [Guest permissions](../user/permissions.md) +on the repository. ### Internal projects Internal projects can be cloned by any logged in user. -They will also be listed on the public access directory (`/public`) for logged +They will also be listed in the public access directory (`/public`), but only for logged in users. -Any logged in user will have [Guest](../user/permissions.md) permissions +Any logged in user will have [Guest permissions](../user/permissions.md) on the repository. ### Private projects -Private projects can only be cloned and viewed by project members, and -they will only appear to project members on the public access directory -(`https://gitlab.example.com/public`). +Private projects can only be cloned and viewed by project members. + +They will appear in the public access directory (`/public`) for project members only. ### How to change project visibility @@ -76,3 +75,15 @@ snippet: This is useful to prevent people exposing their repositories to public by accident. The restricted visibility settings do not apply to admin users. + +<!-- ## Troubleshooting + +Include any troubleshooting steps that you can foresee. If you know beforehand what issues +one might have when setting this up, or when something is changed, or on upgrading, it's +important to describe those, too. Think of things that may go wrong and include them here. +This is important to minimize requests for support, and to avoid doc comments with +questions that you know someone might ask. + +Each scenario can be a third-level heading, e.g. `### Getting error message X`. +If you have none to add when creating a doc, leave this section in place +but commented out to help encourage others to add to it in the future. --> |