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 Serverless. For information about removing a user from your InfluxDB Cloud Serverless 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

Flag Description Input type Maps to ?
-h --help Help for the remove command
--host HTTP address of InfluxDB (default http://localhost:8086) string INFLUX_HOST
--http-debug Inspect communication with InfluxDB servers. string
-i --id Organization ID string INFLUX_ORG_ID
-m --member Member ID string
-n --name Organization name string INFLUX_ORG
--skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
-t --token API token string INFLUX_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 Serverless