Blocking and unblocking users
GitLab administrators block and unblock users.
Blocking a user
In order to completely prevent access of a user to the GitLab instance, administrators can choose to block the user.
Users can be blocked via an abuse report, or directly from the Admin Area. To do this:
- Navigate to Admin Area > Overview > Users.
- Select a user.
- Under the Account tab, click Block user.
A blocked user:
- Will not be able to login.
- Cannot access Git repositories or the API.
- Will not receive any notifications from GitLab.
- Will not be able to use slash commands.
Personal projects, and group and user history of the blocked user will be left intact.
Users can also be blocked using the GitLab API.
Note:
A blocked user does not consume a seat.
Unblocking a user
A blocked user can be unblocked from the Admin Area. To do this:
- Navigate to Admin Area > Overview > Users.
- Click on the Blocked tab.
- Select a user.
- Under the Account tab, click Unblock user.
Users can also be unblocked using the GitLab API.
Note:
Unblocking a user will change the user’s state to active and it consumes a
seat.
Help and feedback
If there's something you don't like about this feature
To propose functionality that GitLab does not yet offer
To further help GitLab in shaping new features
If you didn't find what you were looking for
If you want help with something very specific to your use case, and can use some community support
POST ON GITLAB FORUM
If you have problems setting up or using this feature (depending on your GitLab subscription)
REQUEST SUPPORT
To view all GitLab tiers and features or to upgrade
If you want to try all features available in GitLab.com
If you want to try all features available in GitLab self-managed
If you spot an error or a need for improvement and would like to fix it yourself in a merge request
EDIT THIS PAGE
If you would like to suggest an improvement to this doc