privy policies update
Rename an unowned policy and verify the change.
privy policies update [options] <policy-id>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
policy-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. |
--name <string> |
Policy or rule display name (1–50 characters). |
--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 policies update <policy-id> --name payout-guard --diffprivy policies update <policy-id> --name payout-guard --yesBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Before it runs: Read app environment; existing policies must have owner_id: null. Policy deletion also requires exact name and deletable: true.
- Production apps: Requires
--allow-productionin addition to--yes. - Verification: Fresh policy read and field comparison; deletion requires verified absence.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema policies 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.