Skip to content
CLIUnofficial

privy config account-merging update

Configure future same-email login linking with explicit identity-impact acknowledgement.

Usage

Section titled “Usage”
Terminal window
privy config account-merging update [options]

Options

Section titled “Options”
Option Description
--dry-run Validate and print the API request without network access or credentials.
--allow-access-change Acknowledge cross-app access or customer authentication impact.
--confirm-name <name> Exact selected app name, verified against fresh state.
--yes Confirm this mutation or export.
--body <json> JSON body, or - to read stdin.
--file <path> JSON body file, or - to read stdin.
--merge-accounts-by-email <boolean> Merge customer identities sharing an email across login methods on subsequent logins. Does not retroactively merge existing separate users; changing back does not undo identities already linked.
--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”
Terminal window
privy config account-merging update --merge-accounts-by-email false --diff

Behavior

Section titled “Behavior”
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Caution: Merging affects future identity linking, not undo of existing links. hCaptcha requires compatible frontend SDKs (React react-auth@3.9.0+); incompatible SDKs can stop login.
Section titled “Related guides”

Inspect the full contract locally with privy schema config account-merging 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.