Documentation

Invite a new user

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 invite new users to Telegraf Controller by generating an invite link with a pre-assigned role and expiration. The invited user opens the link, sets a password, and their account is immediately active.

You must have the Owner or Administrator role to create invites.

Create an invite

  1. Navigate to the Users page.
  2. Click the Invite User button.
  3. Enter a Username for the new user (3–50 characters).
  4. Enter the user’s Email address.
  5. Select a Role for the new user:
    • Administrator – full access to all resources and user management.
    • Manager – can manage configurations, agents, and labels but cannot manage users.
    • Viewer – read-only access to all resources.
  6. Set the invite Expiration in hours. The default is 72 hours. Valid values range from 1 to 720 hours (30 days).
  7. Click Create Invite.
Telegraf Controller invite user form

You cannot invite a user with the Owner role. To make someone the owner, first invite them as an Administrator, then transfer ownership.

After creating the invite, Telegraf Controller displays a unique invite link. Copy the link and share it with the user through your preferred communication channel (email, chat, etc.).

The link expires after the duration you configured. Once expired, the link can no longer be used and you must create a new invite.

Accept an invite

The invited user completes the following steps to activate their account:

  1. Open the invite link in a browser.
  2. Set a password that meets the configured complexity requirements.
  3. Click Create Account.

The account activates immediately and the user is automatically logged in with the role assigned during the invite.

Manage pending invites

You can view and manage all pending invites from the Users page. Pending invites appear in a separate list above active users.

To revoke a pending invite before it is used:

  1. Navigate to the Users page.
  2. Locate the pending invite you want to remove.
  3. Click the Delete button next to the invite.
  4. Confirm the deletion when prompted.

Deleting a pending invite invalidates the invite link. The invited user can no longer use it to create an account.


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