Documentation

Reassign a token

Reassigning an API token from one user to another in Telegraf Controller lets you transfer ownership of that token to another user without disrupting any external clients using the token.

Required permissions

To reassign an API token, you must have the Owner or Administrator role in Telegraf Controller.

Reassign a token

You can reassign an individual token from one user to another directly from the token’s detail view or the tokens list.

  1. In Telegraf Controller, navigate to the API Tokens page or open the detail page for the token you want to reassign.
  2. Click Reassign on the token you want to transfer. If on the token detail page, select the Manage tab to reveal the Reassign action.
  3. In the dialog that appears, select the target user you want to assign the token to.
  4. Click Confirm to complete the reassignment.

When you reassign a token, its permissions are automatically restricted to match the target user’s role. For example, a token with full access reassigned to a Viewer becomes a read-only token.

Bulk reassign

If you need to reassign multiple tokens at once, use the bulk reassign option.

  1. On the API Tokens page, select the checkboxes next to the tokens you want to reassign.
  2. Click the Reassign option in the bulk actions bar.
  3. Select the target user you want to assign the selected tokens to.
  4. Click Confirm to reassign all selected tokens.

The same permission restriction applies during bulk reassignment. Each token’s permissions are adjusted to align with the target user’s role.

When to reassign

Reassigning tokens lets you transfer ownership without revoking and recreating tokens. This is useful in several common scenarios:

  • Offboarding a user: A user is leaving the organization and their tokens should continue working under another account. Reassigning ensures active integrations are not disrupted.
  • Reorganizing responsibilities: Team members are shifting roles or responsibilities and token ownership should reflect the new structure.
  • Consolidating ownership after role changes: After updating user roles, you may want to consolidate tokens under a single account to simplify token management.

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