Commit d7318a56 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'improve-public_access-documentation' into 'master'

Add an image to the public access documentation and fix wrong profile path

See merge request !8583
parents 6669bfd3 621b23da
doc/public_access/img/restrict_visibility_levels.png

24 KB

...@@ -52,7 +52,7 @@ for anonymous users. The group page now has a visibility level icon. ...@@ -52,7 +52,7 @@ for anonymous users. The group page now has a visibility level icon.
## Visibility of users ## 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. you are logged in or not.
When visiting the public page of a user, you can only see the projects which When visiting the public page of a user, you can only see the projects which
...@@ -60,10 +60,13 @@ you are privileged to. ...@@ -60,10 +60,13 @@ you are privileged to.
If the public level is restricted, user profiles are only visible to logged in users. If the public level is restricted, user profiles are only visible to logged in users.
## Restricting the use of public or internal projects ## Restricting the use of public or internal projects
In the Admin area under **Settings** (`/admin/application_settings`), you can 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 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:
![Restrict visibility levels](img/restrict_visibility_levels.png)
This is useful to prevent people exposing their repositories to public
by accident. The restricted visibility settings do not apply to admin users. by accident. The restricted visibility settings do not apply to admin users.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment