--- stage: Manage group: Access info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: howto --- # Activating and deactivating users GitLab administrators can deactivate and activate users. ## Deactivating a user > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/22257) in GitLab 12.4. In order to temporarily prevent access by a GitLab user that has no recent activity, administrators can choose to deactivate the user. Deactivating a user is functionally identical to [blocking a user](blocking_unblocking_users.md), with the following differences: - It does not prohibit the user from logging back in via the UI. - Once a deactivated user logs back into the GitLab UI, their account is set to active. A deactivated user: - 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 deactivated user will be left intact. A user can be deactivated from the Admin Area. To do this: 1. Navigate to **Admin Area > Overview > Users**. 1. Select a user. 1. Under the **Account** tab, click **Deactivate user**. Please note that for the deactivation option to be visible to an admin, the user: - Must be currently active. - Must not have signed in, or have any activity, in the last 90 days. Users can also be deactivated using the [GitLab API](../../api/users.md#deactivate-user). NOTE: A deactivated user does not consume a [seat](../../subscriptions/self_managed/index.md#billable-users). ## Activating a user > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/22257) in GitLab 12.4. A deactivated user can be activated from the Admin Area. To do this: 1. Navigate to **Admin Area > Overview > Users**. 1. Click on the **Deactivated** tab. 1. Select a user. 1. Under the **Account** tab, click **Activate user**. Users can also be activated using the [GitLab API](../../api/users.md#activate-user). NOTE: Activating a user changes the user's state to active and consumes a [seat](../../subscriptions/self_managed/index.md#billable-users). NOTE: A deactivated user can also activate their account themselves by simply logging back in via the UI.