---
title: Disable a user
description: Disable a user account to prevent login without deleting the account or its associated tokens.
url: https://docs.influxdata.com/telegraf/controller/users/disable/
estimated_tokens: 1179
product: Telegraf
version: v1
---

# Disable a user

#### Telegraf Controller is in Public Beta

Telegraf Controller is in public beta and will be part of the future Telegraf Enterprise offering. While in beta, Telegraf Controller is **not meant for production use**. The Telegraf Controller documentation is a work in progress, and we are actively working to improve it. If you have any questions or suggestions, please [submit an issue](https://github.com/influxdata/docs-v2/issues/new?labels=Telegraf%20Controller). We welcome any and all contributions.

Beta expectations

-   **No configuration or agent limits**  
    While in beta, Telegraf Controller doesn't place any limits on the number of configurations you can store or the number of Telegraf agents you can track. However, upon being generally available, the free distribution of Telegraf Controller will have limits introduced, with the option to increase limits through a Telegraf Enterprise license.
-   **Potential breaking changes**  
    While in beta, we will do our best to no longer make breaking changes to Telegraf Controller, however, they may be necessary. The majority of changes we make will be additive and non-breaking, and include any necessary migrations. When we do need to make breaking changes, we will do our best to communicate them clearly and in advance to minimize disruption.
-   **Flexible release schedule**  
    While in beta, we will continue to create new releases of Telegraf Controller, but likely at irregular intervals. We will provide [Telegraf Controller release notes](/telegraf/controller/reference/release-notes/) to make it easy to track updates.

Provide beta feedback

-   Use the **Feedback** feature in the Telegraf Controller UI.
-   [Join the InfluxDB Community Slack](https://influxdata.com/slack) and post feedback in the **#telegraf-enterprise-alpha** channel.
-   Post feedback in the [InfluxData Community](https://community.influxdata.com).

Join our public channels

-   [InfluxDB Community Slack *(Preferred)*](https://influxdata.com/slack)
-   [InfluxData Community](https://community.influxdata.com)
-   [InfluxDB Subreddit](https://reddit.com/r/influxdb)

Disabling a user prevents them from logging in without permanently deleting their account or tokens. This is useful when you want to temporarily revoke access or are unsure whether to delete the account.

## What disabling does

When you disable a user account in Telegraf Controller:

-   The user cannot log in to the web interface.
-   All active sessions are destroyed immediately.
-   Existing API tokens remain in the system but cannot be used for authentication while the user is disabled.
-   The user’s data (account details, token records) is preserved.

## Disable a user

1. Navigate to the user’s detail page.
2. Toggle the user’s status to **Disabled** (or click the **Disable** option).
3. Confirm the action.

You cannot disable your own account or the **Owner** account.

## Re-enable a user

1. Navigate to the disabled user’s detail page.
2. Toggle the user’s status to **Active** (or click the **Enable** option).

Once re-enabled, the user can log in immediately with their existing credentials. Their API tokens also become usable again.

#### Related

-   [Authorization](/telegraf/controller/reference/authorization/)