debian-mirror-gitlab/doc/user/admin_area/blocking_unblocking_users.md

49 lines
1.5 KiB
Markdown
Raw Normal View History

2019-12-26 22:10:19 +05:30
---
type: howto
---
# 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](abuse_reports.md#blocking-users),
or directly from the Admin Area. To do this:
1. Navigate to **Admin Area > Overview > Users**.
1. Select a user.
1. 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](../../integration/slash_commands.md).
Personal projects, and group and user history of the blocked user will be left intact.
2020-03-09 13:42:32 +05:30
Users can also be blocked using the [GitLab API](../../api/users.md#block-user).
2019-12-26 22:10:19 +05:30
NOTE: **Note:**
2020-04-08 14:13:33 +05:30
A blocked user does not consume a [seat](../../subscriptions/index.md#choosing-the-number-of-users).
2019-12-26 22:10:19 +05:30
## Unblocking a user
A blocked user can be unblocked from the Admin Area. To do this:
1. Navigate to **Admin Area > Overview > Users**.
1. Click on the **Blocked** tab.
1. Select a user.
1. Under the **Account** tab, click **Unblock user**.
2020-03-09 13:42:32 +05:30
Users can also be unblocked using the [GitLab API](../../api/users.md#unblock-user).
2019-12-26 22:10:19 +05:30
NOTE: **Note:**
Unblocking a user will change the user's state to active and it consumes a
2020-04-08 14:13:33 +05:30
[seat](../../subscriptions/index.md#choosing-the-number-of-users).