Manage tokens with InfluxDB 3 Explorer

How you install Explorer depends on your InfluxDB 3 server

Starting with InfluxDB 3 Enterprise v3.11, Explorer is included with the server and runs as WebAssembly (WASM)–there’s no separate container to install. For InfluxDB 3 Core, or Enterprise earlier than v3.11, Explorer runs as a standalone Docker container. See Install Explorer to find the instructions for your server.

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 the token used in the InfluxDB 3 server configuration is an admin token. If you’re running the Docker container, Explorer must also be running in admin mode.

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:

Admin Token Resource Token (Enterprise only)

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!