Documentation

Update an organization

Use the influx command line interface (CLI) or the InfluxDB user interface (UI) to update an organization.

Note that updating an organization’s name will affect any assets that reference the organization by name, including the following:

  • Queries
  • Dashboards
  • Tasks
  • Telegraf configurations
  • Templates

If you change an organization name, be sure to update the organization in the above places as well.

Update an organization in the InfluxDB UI

  1. In the navigation menu on the left, click the user icon > About.

  2. Click Rename. A verification window appears.

  3. Review the information, and then click I understand, let’s rename my organization.

  4. Enter a new name for your organization, and then click Change organization name.

Update an organization using the influx CLI

Use the influx org update command to update an organization. Provide the following:

  • An operator token using your influx CLI connection configuration, INFLUX_TOKEN environment variable, or the --token, -t flag.
  • The ID of the organization to update using the --org-id, -i flag.
  • Optional: The updated name for the organization with the --name, -n flag.
  • Optional: The updated description for the organization with the --description, -d flag.
Update the name of an organization
influx org update \
  --org-id 
ORG_ID
\
--name
NEW_ORG_NAME
\
--description
NEW_ORG_DESCRIPTION
\

Replace the following:

  • ORG_ID: The ID of the organization to update.
  • NEW_ORG_NAME: The new name for the organization.
  • NEW_ORG_DESCRIPTION: The new description for the organization.

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.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: