Skip to content

gplay team users set

Replace <email>'s account-wide permissions declaratively via users.patch — the whole set is sent, not merged. Express the set in friendly form: --role <bundle> XOR --permissions <alias,…> (account scope). Run gplay team permissions to list aliases and bundles.

A bare set (no --role, --permissions, or --clear) is refused (exit 2) so a forgotten flag can never silently blank the permissions; empty them on purpose with --clear. A permission-reducing set is a normal previewable statement (not gated); conferring admin still requires the named --grant-admin (exit 3).

Use --dry-run to preview the resolved payload with no HTTP; with --output json it emits a requires array naming any safety flag the live write needs.

gplay team users set <email> [flags]
FlagDescription
--clearreplace the permission set with an empty set
--developer-id stringPlay Console Developer account id (overrides the active Account's, env, and project-local)
--dry-runpreview the resolved payload without any HTTP call
--grant-adminacknowledge conferring admin (required when the permission set includes admin)
--output stringoutput format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI)
--permissions stringspermission aliases or raw CAN_* enums (repeatable or comma-separated)
--role stringrole bundle to set (viewer, reviewer, tester-manager, release-manager, admin)
FlagDescription
--account stringname of a stored Account to use (overrides env and active Account)
--retry intretry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry)
--service-account stringpath to a service-account JSON, or inline JSON content (overrides --account, env, and active Account)
--timeout durationper-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads)
-v, --verboselog flow steps to stderr (info level)