privy users freeze
Freeze user access and revoke sessions; verify frozen_at.
privy users freeze [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. |
--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 users freeze <user-id> --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 users are looked up by exact ID before mutations.
- Production apps: Requires
--allow-productionand--yes. - Verification: Read-back where observable; bulk jobs are submissions, not completed imports. Revocation reports observed state without claiming an end-user session exercise.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema users freeze.
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.