Add an image to the public access documentation and fix wrong profile path
Signed-off-by: Rémy Coutable <remy@rymai.me>
This commit is contained in:
parent
e8e2a6a98d
commit
621b23da66
2 changed files with 6 additions and 3 deletions
BIN
doc/public_access/img/restrict_visibility_levels.png
Normal file
BIN
doc/public_access/img/restrict_visibility_levels.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 24 KiB |
|
@ -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:
|
||||
|
||||
![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.
|
||||
|
|
Loading…
Reference in a new issue