gplay team grants set

Grant or adjust <email>'s access to one app (--package) via an upsert: gplay reads the member's current grants, then creates the grant if absent or updates it if present. Express permissions in friendly form — --role <bundle> XOR --permissions <alias,…> — resolved in app scope. Run gplay team permissions --scope app to list them.

Use --dry-run to rehearse: it reads the current state (an idempotent read, no write) and, with --output json, reports the resolved verb (create/update), the permission diff (current → desired, with add/remove), and the requires array. An admin-conferring grant requires the named --grant-admin (exit 3).

Usage

  gplay team grants set <email> --package <pkg> [flags]

Flags

Flag	Description
--developer-id string	Play Console Developer account id (overrides the active Account's, env, and project-local)
--dry-run	rehearse: read current state and report the verb + diff without writing
--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)
--package string	the app (package name) to grant access to
--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

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)