Documentation

influxctl management revoke

The influxctl management revoke command revokes management token access to your InfluxDB cluster. This operation cannot be undone.

Revoked tokens are included when listing tokens

Revoked tokens still appear when listing management tokens, but they are no longer valid for any operations.

Usage

influxctl management revoke [flags] <TOKEN_ID>[ ... TOKEN_ID_N]

Arguments

ArgumentDescription
TOKEN_IDToken ID(s) to revoke access from (space-delimit multiple IDs)

Flags

FlagDescription
--forceDo not prompt for confirmation to revoke
-h--helpOutput command help

Examples

In the examples below, replace the following:

  • TOKEN_ID*: Token ID to revoke access from.

Revoke access from a management token

influxctl management revoke 
TOKEN_ID

Revoke access from multiple management tokens

influxctl management revoke 
TOKEN_ID_1
TOKEN_ID_2

Revoke access from a token and skip confirmation

influxctl management revoke --force 
TOKEN_ID

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2