Documentation

Manage admin tokens

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

Admin tokens can create, edit, and delete other admin tokens.

InfluxDB 3 Core 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 Core instance can have one operator token and unlimited named admin tokens.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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