Documentation

Manage tokens with InfluxDB 3 Explorer

InfluxDB 3 Explorer is Generally Available

InfluxDB 3 Explorer is generally available and is ready for production use. We welcome and encourage your input about your experience with Explorer and invite you to join our public channels for updates and to share feedback.

The InfluxDB 3 Explorer 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.

InfluxDB 3 Explorer lets you manage authorization tokens for your InfluxDB 3 Core instance or InfluxDB 3 Enterprise cluster.

Using InfluxDB 3 Explorer to manage authorization tokens in InfluxDB 3 requires that Explorer is running in admin mode and that the token used in the InfluxDB 3 server configuration is an admin token.

To manage InfluxDB authorization tokens, navigate to Manage Tokens in Explorer. This page provides a list of databases in the connected InfluxDB 3 server that contains the database name, retention period, and number of tables (which includes system tables).

Create a token

Use InfluxDB 3 Explorer to create an admin token or a resource token (Enterprise only) for your InfluxDB 3 instance or cluster.

For more information about InfluxDB tokens, see:

To create an admin token:

  1. On the Manage Databases page, click + Create New.
  2. Select Admin Token to create an admin token.
  3. Provide a Token Name.
  4. Click Create Admin Token.
  5. Copy the generated token string and store it in a secure place.

To create a resource token with read or write permissions for specific databases:

  1. On the Manage Databases page, click + Create New.

  2. Select Database Token to create a resource token (InfluxDB 3 Enterprise only).

  3. Provide a Token Name.

  4. (Optional) Select a Token Expiry.

  5. Select Database Permissions to assign to the token.

    To grant the token read or write permissions on all databases, select the Read and Write column headings. To grant permissions for specific databases, select the checkboxes next to each respective database name.

  6. Copy the generated token string and store it in a secure place.

Store tokens in a secure secret store

This is the only time you are able to view and copy the raw token string. We recommend storing tokens in a secure secret store.

Delete a token

On the Manage Databases page, click the button on the row of the token you want to delete.

Deleting a token is a destructive action and cannot be undone. Any clients using the deleted token will no longer be able to access your InfluxDB 3 instance.

You cannot delete the _admin token

When using InfluxDB 3 Enterprise, the first token created in the cluster is named _admin. This functions as the “operator” token and cannot be deleted.


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Read more

New in InfluxDB 3.2

Key enhancements in InfluxDB 3.2 and the InfluxDB 3 Explorer UI is now generally available.

See the Blog Post

InfluxDB 3.2 is now available for both Core and Enterprise, bringing the general availability of InfluxDB 3 Explorer, a new UI that simplifies how you query, explore, and visualize data. On top of that, InfluxDB 3.2 includes a wide range of performance improvements, feature updates, and bug fixes including automated data retention and more.

For more information, check out: