Skip to content
CLIUnofficial

privy organizations create

Create an app-scoped organization with a default quorum and optional wallet bindings.

Usage

Section titled “Usage”
Terminal window
privy organizations create [options]

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.
--wallet-ids <json> Existing unbound wallet IDs to associate. Organization bindings cannot subsequently be changed.
--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”
Terminal window
privy organizations create --display-name Treasury --default-key-quorum-id <id> --dry-run
privy organizations create --file organization.json --yes

Behavior

Section titled “Behavior”
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Before it runs: Check app environment, existing organization/quorum and optional unbound wallets.
  • Production apps: Requires --allow-production and --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.
Section titled “Related guides”

Inspect the full contract locally with privy schema organizations create.

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.