---
title: Revoke a token
description: Revoke an API token to immediately prevent its use while keeping the token record for auditing.
url: https://docs.influxdata.com/telegraf/controller/tokens/revoke/
estimated_tokens: 1424
product: Telegraf
version: v1
---

# Revoke a token

#### 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)

Revoking a token immediately prevents it from being used for authentication while keeping the token record in the system for auditing purposes. Unlike deletion, revocation preserves a full history of the token, including when it was created and when it was disabled.

## Revoke versus delete

Telegraf Controller supports two ways to remove a token from active use: **revocation** and **deletion**.

-   **Revoked** tokens remain visible in the token list with a **Revoked** status. This provides an audit trail showing when the token was created and when it was disabled. Revoked tokens cannot be used for authentication.
-   **Deleted** tokens are permanently removed from the system. No record of the token is retained after deletion.

Use revoke when you want to disable a token but maintain an audit trail. Use delete when you want to completely remove the token and its record from the system.

For more information about deleting a token, see [Delete a token](/telegraf/controller/tokens/delete/).

## Revoke a token

1. Navigate to the **API Tokens** page, or open the token’s detail view.
2. Click **Revoke**. If on the token detail page, select the **Manage** tab to reveal the **Revoke** action.
3. Confirm the revocation in the dialog.

The token status changes to **Revoked** and any requests that use the token are immediately rejected.

#### You cannot reactivate a revoked token

Revocation is permanent. You cannot re-activate a revoked token. If you need to restore access, create a new token. See [Create a token](/telegraf/controller/tokens/create/).

## Bulk revoke

To revoke multiple tokens at once:

1. On the **API Tokens** page, select the tokens you want to revoke.
2. Click **Revoke** in the bulk actions bar.
3. Confirm the revocation in the dialog.

All selected tokens are immediately revoked and can no longer be used for authentication.

#### Related

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