Skip to content
Back to skills

Gplay Team

ASecurity

Developer account members and permissions with `gplay team`. Use when inviting or off-boarding a member, auditing what a member can do, granting per-app access, or looking up a permission alias or role bundle (`team permissions`, offline).

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 13, 2026
ai-agentsbash

Works with

  • cli

Security analysis

A100/100

Scanned October 13, 2026

npx -y skills add PollyGlot/google-play-cli-skills --skill gplay-team --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gplay Team?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gplay Team
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pollyglot-gplay-team/badge)](https://www.skillsdirectory.com/skills/pollyglot-gplay-team)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gplay-team
description: Developer account members and permissions with `gplay team`. Use when inviting or off-boarding a member, auditing what a member can do, granting per-app access, or looking up a permission alias or role bundle (`team permissions`, offline).
---

# 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`.

## Per-app access grants

```bash
gplay team grants list
gplay team grants set alice@example.com --package com.example.app --role reviewer      # upsert; admin needs --grant-admin
gplay team grants remove alice@example.com --package com.example.app --confirm         # drops one app, keeps the membership
```

`grants set --dry-run --output json` reports the resolved verb (create/update)
and the permission diff beside `requires`.

## Developer account addressing

Commands address the Developer account id recorded by `gplay auth login
--developer-id`; the override cascade (`--developer-id`) is in
`gplay-cli-usage`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.