Documentation

Update users

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

Owners and administrators can reset passwords and change roles for other users in Telegraf Controller. These actions help maintain account security and ensure users have the appropriate level of access.

Reset a user’s password

When a user forgets their password or needs a credential refresh, you can generate a time-limited reset link for them.

You must have the Owner or Administrator role to reset passwords. Only the Owner can reset Administrator passwords.

  1. Navigate to the user’s detail page.
  2. Click Reset Password.
  3. Set the link expiration. The default is 24 hours, but you can configure it from 1 to 720 hours.
  4. Click Generate Link to create the reset link.
  5. Copy the generated reset link and share it with the user through a secure channel.

Complete a password reset

After receiving a reset link, the user completes the following steps:

  1. Open the reset link in a browser.
  2. Enter a new password that meets the complexity requirements.
  3. Click Submit to save the new password.

The user is not automatically logged in after resetting their password. They must log in with their new credentials.

Emergency owner password reset

If the owner account is locked out or the owner has forgotten their password, you can reset it using environment variables.

  1. Set the following environment variables:
    • RESET_OWNER_PASSWORD=true
    • OWNER_PASSWORD to the desired new password
  2. Restart the Telegraf Controller application.
  3. Log in with the new password.
  4. Remove the RESET_OWNER_PASSWORD and OWNER_PASSWORD environment variables.

Remove RESET_OWNER_PASSWORD and OWNER_PASSWORD environment variables after successfully logging in. Leaving them set causes the password to reset on every application restart.

Change a user’s role

You can promote or demote users by changing their assigned role.

You must have the Owner or Administrator role to change a user’s role. Only the Owner can change a user’s role to Administrator.

  1. Navigate to the user’s detail page.
  2. Select the user’s new role.
  3. Confirm the change when prompted.

The following restrictions apply to role changes:

  • You cannot assign the Owner role directly. To make a user the owner, the current owner must transfer ownership.

Side effects of changing a user’s role

  • The user’s API tokens are reclamped to match the new role’s permissions. If the new role cannot manage tokens (such as Viewer), all active tokens are revoked.
  • The user’s active sessions are destroyed. They must log in again to continue using Telegraf Controller.

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