Documentation

Manage users

Manage users and access to resources in your InfluxDB Cloud Dedicated cluster.

By assigning users to different groups based on the level of access they need, you can minimize unnecessary access and reduce the risk of inadvertent actions. User groups associate access privileges with user attributes–an important part of the Attribute-Based Access Control (ABAC) security model which grants access based on user attributes, resource types, and environment context.

Available user groups

In InfluxDB Cloud Dedicated, users have “management” responsibilities, such as creating and deleting databases, viewing resource information, and provisioning database tokens for reading and writing data.

A user can belong to the following groups, each with predefined privileges:

  • Admin: Read and write permissions on all resources.
  • Member: Read permission on certain resources and create permission for database tokens; members can’t delete or create databases or management tokens.
  • Auditor: Read permission on all resources; auditors can’t modify resources.

Existing users are Admin by default

With the release of user groups for InfluxDB Cloud Dedicated, all existing users in your account are initially assigned to the Admin group, retaining full access to resources in your cluster.

User management methods

Choose the appropriate method for your user management needs:

Admin UI (Self-service)

Use the Admin UI for user management tasks (available to Admin users only):

  • View users and invitations - View existing users, invite status, invite ID, and invitation date
  • Invite new users - Send invitations with role assignment (Admin, Member, Auditor)
  • Revoke pending invitations - Cancel invitations that haven’t been accepted

Role permissions

Auditor role users can view the invite list but cannot send or revoke invitations. Member role users cannot access the invite list.

For more information, see Manage users in the Admin UI.

Contact support (Advanced operations)

For operations not available in the Admin UI:

  • View or change user roles after invitation acceptance
  • Remove accepted users from your account
  • Advanced user configurations

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.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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