privy organizations update
Update app organization name or default quorum and verify.
privy organizations update [options] <organization-id>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
organization-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. |
--body <json> |
JSON body, or - to read stdin. |
--file <path> |
JSON body file, or - to read stdin. |
--display-name <string> |
App organization display name. |
--default-key-quorum-id <string> |
Existing default key quorum in this app; controls default organization approvals. |
--diff |
Read live state and show changes WITHOUT writing (requires login). |
--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 organizations update <id> --display-name Treasury --diffprivy organizations update <id> --display-name Treasury --yesBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Before it runs: Check app environment, existing organization/quorum and optional unbound wallets.
- Production apps: Requires
--allow-productionand--yes. - Verification: Exact-ID organization and supplied wallet entity read-back.
- Retries: None.
- Caution: Wallet organization bindings are one-way. App organizations are not developer accounts or teams.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema organizations update.
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.