gplay team users add
Invite <email> as a member of the Developer account with account-wide
permissions, via users.create. Express permissions in friendly form —
--role <bundle> XOR --permissions <alias,…> — resolved in account scope
(the _GLOBAL family). Run gplay team permissions to list aliases and bundles.
add is the routine tier: no confirmation gate, and CI-scriptable. But an admin-conferring add (--role admin, or a permission set including the all-permissions enum) requires the named --grant-admin — handing out full control is never silent.
Use --dry-run to preview the resolved payload with no HTTP; with --output json
it emits a requires array naming the safety flags the live write needs, so
an agent can discover the gate before running it.
gplay team users add <email> [flags]| Flag | Description |
|---|---|
--developer-id string | Play Console Developer account id (overrides the active Account's, env, and project-local) |
--dry-run | preview the resolved payload without any HTTP call |
--grant-admin | acknowledge conferring admin (required when the permission set includes admin) |
--output string | output format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI) |
--permissions strings | permission aliases or raw CAN_* enums (repeatable or comma-separated) |
--role string | role bundle to grant (viewer, reviewer, tester-manager, release-manager, admin) |
Global flags
Section titled “Global flags”| Flag | Description |
|---|---|
--account string | name of a stored Account to use (overrides env and active Account) |
--retry int | retry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry) |
--service-account string | path to a service-account JSON, or inline JSON content (overrides --account, env, and active Account) |
--timeout duration | per-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads) |
-v, --verbose | log flow steps to stderr (info level) |