2016-12-25 06:16:14 +01:00
|
|
|
|
# Deactivate or reactivate a bot
|
|
|
|
|
|
2017-01-09 05:46:03 +01:00
|
|
|
|
Zulip organization administrators have the ability to deactivate or reactivate any bots
|
|
|
|
|
in their organization.
|
2016-12-25 06:16:14 +01:00
|
|
|
|
|
|
|
|
|
## Deactivate a bot
|
|
|
|
|
|
|
|
|
|
To properly remove a bot’s access to a Zulip organization, it does not suffice
|
|
|
|
|
to deactivate it in the SSO system, since that action does not prevent
|
|
|
|
|
authentication with any API keys the bot has.
|
|
|
|
|
|
|
|
|
|
Instead, you should deactivate the bot using the Zulip administration interface.
|
|
|
|
|
|
2017-01-04 04:09:15 +01:00
|
|
|
|
{!go-to-the.md!} [Bots](/#administration/bot-list-admin)
|
|
|
|
|
{!admin.md!}
|
2016-12-25 06:16:14 +01:00
|
|
|
|
|
2017-01-04 04:09:15 +01:00
|
|
|
|
4. Click the **Deactivate** button to the right of the bot that you want to
|
|
|
|
|
deactivate.
|
2016-12-25 06:16:14 +01:00
|
|
|
|
|
2017-01-04 04:09:15 +01:00
|
|
|
|
5. After clicking the **Deactivate** button, the button will transform into a
|
|
|
|
|
**Reactivate** button, and the **Name** and **Email** of the bot will be
|
|
|
|
|
stricken through, confirming the success of the bot's deactivation.
|
2016-12-25 06:16:14 +01:00
|
|
|
|
|
|
|
|
|
## Reactivate a bot
|
|
|
|
|
|
2017-01-09 05:46:03 +01:00
|
|
|
|
Zulip organization administrators can choose to reactivate a deactivated bot by
|
2016-12-25 06:16:14 +01:00
|
|
|
|
following the following steps.
|
|
|
|
|
|
2017-01-04 04:09:15 +01:00
|
|
|
|
{!go-to-the.md!} [Bots](/#administration/bot-list-admin)
|
|
|
|
|
{!admin.md!}
|
2016-12-25 06:16:14 +01:00
|
|
|
|
|
2017-01-04 04:09:15 +01:00
|
|
|
|
4. In the **Bots** section, click the **Reactivate** button to the right of the
|
|
|
|
|
bot that you want to reactivate.
|
2016-12-25 06:16:14 +01:00
|
|
|
|
|
2017-01-04 04:09:15 +01:00
|
|
|
|
5. After clicking the **Reactivate** button, the button will transform into a
|
|
|
|
|
**Deactivate** button, and the **Name** and **Email** of the bot will be cleared
|
|
|
|
|
of strikethrough, confirming the success of the bot's reactivation.
|