2016-12-24 18:43:20 +01:00
|
|
|
|
# Deactivate or reactivate a user
|
|
|
|
|
|
2017-01-17 18:54:19 +01:00
|
|
|
|
{!admin-only.md!}
|
|
|
|
|
|
2018-07-10 19:30:37 +02:00
|
|
|
|
## Deactivate (ban) a user
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
2018-07-10 19:30:37 +02:00
|
|
|
|
To properly remove a user’s access to a Zulip organization, it does not
|
|
|
|
|
suffice to change their password or deactivate their account in an external
|
|
|
|
|
email system, since the user’s API key and bot API keys will still be
|
|
|
|
|
active. Instead, you need to deactivate the user’s account using the Zulip
|
2018-09-15 00:57:06 +02:00
|
|
|
|
administrative interface.
|
2017-04-07 21:39:58 +02:00
|
|
|
|
|
2020-06-10 22:33:48 +02:00
|
|
|
|
Note that organization administrators cannot deactivate organization owners.
|
|
|
|
|
|
2019-04-03 01:17:21 +02:00
|
|
|
|
{start_tabs}
|
|
|
|
|
|
2022-03-15 15:30:16 +01:00
|
|
|
|
{tab|via-user-profile}
|
|
|
|
|
|
|
|
|
|
1. Hover over a user's name in the right sidebar.
|
|
|
|
|
|
|
|
|
|
1. Click on the ellipsis (<i class="zulip-icon zulip-icon-ellipsis-v-solid"></i>)
|
|
|
|
|
to the right of their name.
|
|
|
|
|
|
|
|
|
|
1. Click **Manage this user**.
|
|
|
|
|
|
|
|
|
|
1. Click the **Deactivate user** button at the bottom.
|
|
|
|
|
|
|
|
|
|
1. Approve by clicking **Confirm**.
|
|
|
|
|
|
|
|
|
|
{tab|via-organization-settings}
|
|
|
|
|
|
2018-04-25 03:54:09 +02:00
|
|
|
|
{settings_tab|user-list-admin}
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
2022-03-15 15:30:16 +01:00
|
|
|
|
1. Click the **Deactivate** button to the right of the user account that you
|
|
|
|
|
want to deactivate.
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
2022-03-15 15:30:16 +01:00
|
|
|
|
1. Approve by clicking **Confirm**.
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
2019-04-03 01:17:21 +02:00
|
|
|
|
{end_tabs}
|
|
|
|
|
|
2018-07-10 19:30:37 +02:00
|
|
|
|
The user will be logged out immediately and not be able to log back in. The
|
|
|
|
|
user's bots will also be deactivated. Lastly, the user will be unable to
|
|
|
|
|
create a new Zulip account in your organization using their deactivated
|
|
|
|
|
email address.
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
|
|
|
|
## Reactivate a user
|
|
|
|
|
|
2022-07-07 07:09:12 +02:00
|
|
|
|
Organization administrators can reactivate a deactivated user. The reactivated
|
|
|
|
|
user will have the same role, stream subscriptions, user group memberships, and
|
|
|
|
|
other settings and permissions as they did prior to deactivation. They will also
|
|
|
|
|
have the same API key and bot API keys, but the bots will be deactivated until
|
|
|
|
|
the user manually [reactivates](deactivate-or-reactivate-a-bot) them again.
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
2019-04-03 01:17:21 +02:00
|
|
|
|
{start_tabs}
|
|
|
|
|
|
2018-04-25 03:54:09 +02:00
|
|
|
|
{settings_tab|deactivated-users-admin}
|
2016-12-24 18:43:20 +01:00
|
|
|
|
|
2017-01-04 03:55:45 +01:00
|
|
|
|
4. Click the **Reactivate** button to the right of the user account that you
|
|
|
|
|
want to reactivate.
|
2019-04-03 01:17:21 +02:00
|
|
|
|
|
|
|
|
|
{end_tabs}
|
2022-07-07 07:09:12 +02:00
|
|
|
|
|
|
|
|
|
!!! tip ""
|
|
|
|
|
You may want to [review and adjust](/help/manage-user-stream-subscriptions)
|
|
|
|
|
the reactivated user's stream subscriptions.
|