privy accounts members remove
Remove a dashboard member only after protected-account, last-admin and quorum dependency checks.
privy accounts members remove [options] <user-id>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
user-id |
— |
Options
Section titled “Options”| Option | Description |
|---|---|
--dry-run |
Validate and print the API request without network access or credentials. |
--yes |
Confirm this mutation or export. |
--confirm-account <name> |
Exact account name; this is an account-wide mutation. |
--allow-self-impact |
Explicitly acknowledge changing/removing your own membership; last-admin guard still applies. |
--body <json> |
JSON body, or - to read stdin. |
--file <path> |
JSON body file, or - to read stdin. |
--allow-production |
Explicitly allow this production mutation; also requires --yes. |
Global options such as --app, --account and --profile also apply. See the command reference overview.
Examples
Section titled “Examples”privy accounts members remove <dashboard-user-id> --account <account-id> --dry-runBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: account
- Before it runs: Fresh account state; refuse if any protected app; last admin/self-impact/dependency checks.
- Production apps: Accounts containing production apps require
--allow-production. - Verification: Fresh account membership/invitation read-back.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema accounts members remove.
Privy CLI is an unofficial, community project by Samarth Saxena. Not affiliated with or endorsed by Privy. The Privy name and wordmark belong to Privy. It uses undocumented dashboard APIs that can change.