You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/book/04-git-server/chapter4.asc
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -647,20 +647,36 @@ Once logged in, click the ``Admin area'' icon in the menu at the top right.
647
647
.The ``Admin area'' item in the GitLab menu.
648
648
image::images/gitlab-menu.png[The ``Admin area'' item in the GitLab menu.]
649
649
650
-
===== Users and Groups
651
-
* Users
650
+
===== Users
651
+
652
+
Users in GitLab are accounts that correspond to people.
653
+
User accounts don't have a lot of complexity.
654
+
Mainly it's a collection of personal information attached to login data.
655
+
Each user account comes with a *namespace*, which is a logical grouping of projects that belong to that user.
656
+
If the user +jane+ had a project named +project+, that project's url would be http://hostname.tld/jane/project[].
652
657
653
658
[[gitlab_users]]
654
659
.The GitLab user administration screen.
655
660
image::images/gitlab-users.png[The GitLab user administration screen.]
656
661
657
-
* Groups
662
+
Removing a user can be done in two ways.
663
+
``Blocking'' a user prevents them from logging into the GitLab instance, but all of the data under that user's namespace will be preserved, and commits signed with that user's email address will still link back to their profile.
664
+
665
+
``Destroying'' a user, on the other hand, completely removes them from the database and filesystem. All projects and data in their namespace is removed, and any groups they own will also be removed.
666
+
This is obviously a much more permanent and destructive action, and its uses are rare.
667
+
668
+
===== Groups
669
+
670
+
A GitLab group is an assemblage of projects, along with data about how users can access those projects.
671
+
Each group is a project namespace (the same way that users are), so if the group +training+ had a project +materials+, its url would be http://hostname.tld/training/materials[].
658
672
659
673
[[gitlab_groups]]
660
-
.The GitLab groups administration screen.
661
-
image::images/gitlab-groups.png[The GitLab groups administration screen.]
674
+
.The GitLab group administration screen.
675
+
image::images/gitlab-groups.png[The GitLab group administration screen.]
662
676
663
-
()
677
+
Each group is associated with a number of users, each of which has a level of permissions for the group's projects and the group itself.
678
+
These range from ``Guest'' (issues and chat only) to ``Owner'' (full control of the group and its projects).
679
+
The types of permissions are too numerous to list here, but GitLab has a helpful link on the administration screen.
0 commit comments