diff options
author | Achilleas Pipinellis <axilleas@axilleas.me> | 2016-03-22 13:36:43 +0300 |
---|---|---|
committer | Achilleas Pipinellis <axilleas@axilleas.me> | 2016-03-22 13:36:43 +0300 |
commit | 2adc874fc8145b82b2449a9970a02f3cfaf69ed6 (patch) | |
tree | a6a84a2cc4e03a01fe59d33b232fc3cc17aa2ab1 | |
parent | fc6ee359287c6bd286e32ce808e7069714e1732e (diff) |
Add docs on group visibility
[ci skip]
-rw-r--r-- | doc/public_access/public_access.md | 23 |
1 files changed, 15 insertions, 8 deletions
diff --git a/doc/public_access/public_access.md b/doc/public_access/public_access.md index 6e22ea7b72a..20aa90f0d69 100644 --- a/doc/public_access/public_access.md +++ b/doc/public_access/public_access.md @@ -35,6 +35,21 @@ the repository. 1. Go to your project's **Settings** 1. Change "Visibility Level" to either Public, Internal or Private +## Visibility of groups + +>**Note:** +[Starting with][3323] GitLab 8.6, the group visibility has changed and can be +configured the same way as projects. In previous versions, a group's page was +always visible to all users. + +Like with projects, the visibility of a group can be set to dictate whether +anonymous users, all signed in users, or only explicit group members can view +it. The restriction for visibility levels on the application setting level also +applies to groups, so if that's set to internal, the explore page will be empty +for anonymous users. The group page now has a visibility level icon. + +[3323]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3323 + ## Visibility of users The public page of a user, located at `/u/username`, is always visible whether @@ -43,14 +58,6 @@ you are logged in or not. When visiting the public page of a user, you can only see the projects which you are privileged to. -## Visibility of groups - -The public page of a group, located at `/groups/groupname`, is always visible -to everyone. - -Logged out users will be able to see the description and the avatar of the -group as well as all public projects belonging to that group. - ## Restricting the use of public or internal projects In the Admin area under **Settings** (`/admin/application_settings`), you can |