gplay-teamlisted
Install: claude install-skill PollyGlot/google-play-cli-skills
# gplay team (users + grants + permissions)
Two write surfaces and one offline reference: **account-wide** membership
(`team users`), **per-app** access (`team grants`), and the **permission
vocabulary** (`team permissions`). Shared conventions are in `gplay-cli-usage`.
## Permission vocabulary (start here)
```bash
gplay team permissions --scope app # offline; account scope by default (team users), app scope for team grants
gplay team permissions --output json # marks the admin-conferring alias and bundle
```
Writes take **`--role <bundle>` XOR `--permissions <alias,…>`** (raw `CAN_*`
enums accepted); `team users` resolves in account scope, `team grants` in app
scope.
## Account-wide members
```bash
gplay team users list
gplay team users view alice@example.com # one member: permissions + per-app grants (unknown member: exit 30)
gplay team users add alice@example.com --role release-manager
gplay team users set bob@example.com --permissions CAN_REPLY_TO_REVIEWS_GLOBAL # declaratively replaces the set
gplay team users remove carol@example.com --confirm # off-boarding is destructive: exit 3 without it
```
`add`/`set` have no gate except conferring admin (`--role admin`, or a set
containing the all-permissions enum): `--grant-admin`, exit `3` without it
(ADR-0017). `remove` needs `--confirm`.
Inviting an existing member fails with exit `60`. To make `add` safe to
re-run, pass `--if-exists skip` (leave the member as is) or `--if-exists
update` (converge: