Documentation

Manage tokens with InfluxDB 3 Explorer

InfluxDB 3 Explorer lets you manage authorization tokens for your InfluxDB 3 Core instance or InfluxDB 3 Enterprise cluster.

Using InfluxDB 3 Explorer to manage authorization tokens in InfluxDB 3 requires that Explorer is running in admin mode and that the token used in the InfluxDB 3 server configuration is an admin token.

To manage InfluxDB authorization tokens, navigate to Manage Tokens in Explorer. This page provides a list of databases in the connected InfluxDB 3 server that contains the database name, retention period, and number of tables (which includes system tables).

Create a token

Use InfluxDB 3 Explorer to create an admin token or a resource token (Enterprise only) for your InfluxDB 3 instance or cluster.

For more information about InfluxDB tokens, see:

To create an admin token:

  1. On the Manage Databases page, click + Create New.
  2. Select Admin Token to create an admin token.
  3. Provide a Token Name.
  4. Click Create Admin Token.
  5. Copy the generated token string and store it in a secure place.

To create a resource token with read or write permissions for specific databases:

  1. On the Manage Databases page, click + Create New.

  2. Select Database Token to create a resource token (InfluxDB 3 Enterprise only).

  3. Provide a Token Name.

  4. (Optional) Select a Token Expiry.

  5. Select Database Permissions to assign to the token.

    To grant the token read or write permissions on all databases, select the Read and Write column headings. To grant permissions for specific databases, select the checkboxes next to each respective database name.

  6. Copy the generated token string and store it in a secure place.

Store tokens in a secure secret store

This is the only time you are able to view and copy the raw token string. We recommend storing tokens in a secure secret store.

Delete a token

On the Manage Databases page, click the button on the row of the token you want to delete.

Deleting a token is a destructive action and cannot be undone. Any clients using the deleted token will no longer be able to access your InfluxDB 3 instance.

You cannot delete the _admin token

When using InfluxDB 3 Enterprise, the first token created in the cluster is named _admin. This functions as the “operator” token and cannot be deleted.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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