Topics Map > GitLab

DoIT Shared Tools - GitLab - User Management: Group Owner versus Shared Tools Admins

A Group owner can manage users within their groups and subgroups. Shared Tools Admin can assist group owners in managing their users.

Group Owners and User Management

You are the Owner of a group and have considered creating and organizing your subgroups. There are various roles you can assign to users. The permissions of the role, Owner, allow you to Add and Remove users.


Add Users to a Group

Follow this link to GitLab documentation about adding users.

Remove Users from your Group

Follow this link to GitLab documentation about removing users.

Check whether a specific user is part of any group or subgroup under your ownership

You may identify if a specific user is a member of one or more of the subgroups you own.  The GitLab API provides a way to see a user's memberships within a top-level group: https://docs.gitlab.com/api/members/#list-memberships-for-a-billable-member-of-a-group. 


Shared Tools Admins and User Management

Shared Tools Admins can assist you with your users. They can provide you with a list of the groups and subgroups in which a specific user is a member. Finally, they can Block or Ban a specific user per your request.

Block, Ban users from your Group

As the owner of your group/ subgroups, you may request that the Shared Tools Admins block or ban a user.

The below image shows what the Shared Tools Admins see when they view a specific user. Shared Tools Admins may Block or Ban a user. 


gitlab super admin view of one user


You may request that the Shared Tools Admin:

  • Block

    While you identify which of your groups/subgroups the user in question has access, you may request that a user be Blocked.  A blocked user:

    Cannot sign in or access any repositories.
    Any associated data remains in these repositories.
    Cannot use slash commands.
    Does not occupy a seat.
    Needs to be explicitly unblocked by the Shared Tools Admins, should they work for another part of the UW and need GitLab access.

  • Ban a user

    Should abuse occur, you may request that a user be Banned. A banned user:

    Cannot access the group or any of repositories.
    Cannot use slash commands.
    Does not occupy a seat.
    Needs to be explicitly unbanned by the Shared Tools Admins, should they work for another part of the UW and need GitLab access.


Keywords:
user management block delete add ban group subgroup super admin superadmin abuse trust 
Doc ID:
9359
Owned by:
Teresa A. in Shared Tools
Created:
2009-03-18
Updated:
2025-04-18
Sites:
Shared Tools