diff --git a/doc/public_access/img/restrict_visibility_levels.png b/doc/public_access/img/restrict_visibility_levels.png new file mode 100644 index 0000000000000000000000000000000000000000..c7d4d87981f18d595f894e7b95a29e4b542fd26e Binary files /dev/null and b/doc/public_access/img/restrict_visibility_levels.png differ diff --git a/doc/public_access/public_access.md b/doc/public_access/public_access.md index a3921f1b89f32af853f9984b895236621e30aa45..e8f4c73120ca728243200647f473fd4f122aca31 100644 --- a/doc/public_access/public_access.md +++ b/doc/public_access/public_access.md @@ -52,7 +52,7 @@ for anonymous users. The group page now has a visibility level icon. ## Visibility of users -The public page of a user, located at `/u/username`, is always visible whether +The public page of a user, located at `/username`, is always visible whether you are logged in or not. When visiting the public page of a user, you can only see the projects which @@ -60,10 +60,13 @@ you are privileged to. If the public level is restricted, user profiles are only visible to logged in users. - ## Restricting the use of public or internal projects In the Admin area under **Settings** (`/admin/application_settings`), you can restrict the use of visibility levels for users when they create a project or a -snippet. This is useful to prevent people exposing their repositories to public +snippet: + + + +This is useful to prevent people exposing their repositories to public by accident. The restricted visibility settings do not apply to admin users.