Documentation

Reassign a token

Telegraf Controller is in Public Beta

Telegraf Controller is in public beta and will be part of the future Telegraf Enterprise offering. While in beta, Telegraf Controller is not meant for production use. The Telegraf Controller documentation is a work in progress, and we are actively working to improve it. If you have any questions or suggestions, please submit an issue. We welcome any and all contributions.

Beta expectations

Provide beta feedback

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!


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:

New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

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