Documentation

influx org members remove

Available with InfluxDB OSS 2.x only

The influx org members remove command removes organization members in InfluxDB OSS 2.x, but cannot remove organization members in InfluxDB Cloud. For information about removing a user from your InfluxDB Cloud organization, see Remove a user.

The influx org members remove command removes a member from an organization in InfluxDB.

Usage

influx org members remove [flags]

Flags

FlagDescriptionInput typeMaps to ?
-h--helpHelp for the remove command
--hostHTTP address of InfluxDB (default http://localhost:8086)stringINFLUX_HOST
--http-debugInspect communication with InfluxDB servers.string
-i--idOrganization IDstringINFLUX_ORG_ID
-m--memberMember IDstring
-n--nameOrganization namestringINFLUX_ORG
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-t--tokenAPI tokenstringINFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Remove a member from an organization
influx org members remove \
  --member 00x0oo0X0xxxo000 \
  --name example-org

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:

InfluxDB Cloud powered by TSM