Documentation

Manage admin tokens

Manage InfluxDB 3 Enterprise admin tokens to authorize server actions, influxdb3 CLI commands, and HTTP API endpoints for your InfluxDB 3 Enterprise instance. Administrative (admin) tokens provide full system access and management capabilities for your InfluxDB 3 Enterprise instance.

Admin tokens can create, edit, and delete other admin tokens, as well as manage resource tokens.

InfluxDB 3 Enterprise supports two types of admin tokens:

  • Operator token: A system-generated administrative token with the name _admin.

    • Cannot be edited or deleted
    • Never expires
    • Cannot be recreated if lost (future functionality)
    • Can be regenerated using the CLI
  • Named admin token: User-defined administrative tokens with full admin permissions.

    • Can be created, edited, and deleted
    • Support expiration dates
    • Cannot modify or remove the operator token

An InfluxDB 3 Enterprise instance can have one operator token and unlimited named admin tokens.


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