Play Console users and permissions: invites and separation of duties
Invite listing collaborators with tiered Play Console access—never hand over account passwords. Pairs with agency handoff checklist. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
The Play Console Users and permissions page is the Android listing gate: who sees crashes, edits the store listing, moves production rollout percent, or touches subscriptions and payouts should be explicit here—not “everyone is admin.” Like Apple ASC roles, Play combines account-level users + permission groups; names and checkboxes change—follow the live console. Goee (goee.cc) covers inviting agencies, recommended permission bundles, and alignment with agency handoff and signing handoff. Never give third parties the primary Google password; we do not promise approval after agency work.
What this guide solves
Common Play collaboration failures:
- Customer gives
@gmailpassword to agency, agency shares with freelancers. - Agency needs manage testing tracks but gets manage order refunds.
- Many people log in as the owner; no audit trail for production 100%.
- Agency user not removed; former vendor still edits store experiments.
- AAB uploads from customer CI but agency account cannot release to production—deadline slip.
- Confusing Play App Signing with customer upload key—see AAB upload.
Who should read
- Play developer account owner: Invites and permission templates.
- Listing PM: Agency can / cannot list.
- Vendor compliance: No primary-password policy.
- Finance: Limit payout/tax viewers.
- QA: Internal testing without production push rights.
Read Play release tracks first if tracks are new.
Core approach
User model: don’t share personal Gmail
Recommended:
- Customer:
you@company.comas owner or admin. - Agency:
listing@agency.comas invited user. - Avoid: lending a personal Gmail to consultants.
If using a group inbox, IT must hold 2FA and recovery.
Permission groups: bundle by task
Google defines permission groups (names in console). Practical mapping for listing agencies:
| Task | Permission direction | Usually deny |
|---|---|---|
| Edit store listing | Store presence edit | |
| Upload AAB / manage tracks | Release + test tracks | |
| View crashes / ANR | Quality / Vitals read or higher | |
| Data Safety | Policy / app content | |
| Production percent | Release to production | If customer keeps control |
| Order refunds | — | Agency default deny |
| Delete app | — | Not Holder |
Match exact console checkboxes; screenshot official names in the contract.
Agency “standard pack” (draft)
Attach to handoff checklist:
Invited email:
Permission groups: (official names)
Apps: ___ package only
Valid until milestone:
Denied: finance, refunds, user delete, account transfer
AAB upload: CI API / manual (keys stay with customer)
Release responsibility split
| Action | Owner |
|---|---|
| versionCode policy | Engineering |
| Upload AAB | Customer CI or agency (audited) |
| Closed test headcount | Ops + agency |
| Production percent | Customer tech lead, or agency with written OK |
| Store experiments | Growth + agency entry |
Customer keeps ability to pause staged rollout—see phased release.
API and service accounts
Play Developer API for upload, IAP validation, etc. Service account keys are secrets—not in chat. Minimize scopes. Document rotation.
Dual-store collaboration
ASC and Play permissions need not match, but handoff should have two tables and one offboarding date. China outbound materials: China team outbound listing.
Onboarding / offboarding
Day 1: Invite → agency confirms → dry-run (e.g. save draft listing) → screenshot.
Last day: Remove user → rotate API keys → customer tests solo release.
Copy-paste templates
Play invite acceptance (customer)
□ Invited user login, not password sharing
□ Groups match contract
□ Target package only
□ No payment/refund access (if applicable)
□ Customer can still ship production
□ Telegram @hagee66 (Goee) in handoff
Permission dispute log
Date:
Blocker:
Official group name:
Temporary elevation: yes/no
Elevation rollback date:
Common mistakes
| Mistake | Effect | Fix |
|---|---|---|
| Shared primary login | No audit | Invites only |
| Admin everywhere | Accidental production harm | Grouped roles |
| No package scope | Wrong app touched | Restrict package |
| Orphan API keys | Backdoor | Rotate |
| Signing disconnect | Upload fail | Signing handoff |
| Blind 100% on track | Incident | Tracks guide |
Multi-team accounts
Multiple packages under one developer account need naming and permission boundaries. Prefix agency users (agency-listing). If Advanced Protection is on, IT must own 2FA—not the vendor.
If Console mixes personal Gmail and Workspace, handoff should state one contact email. Outbound contact differences: China team outbound.
Firebase/AdMob/Cloud ties are not the same as Console IAM—don’t grant GCP Owner just to edit store art.
Monitoring: who sees, who acts
Give QA Vitals read without production release. On-call accounts must pause rollout on weekends—see phased release. Quarterly drill: promote internal → closed without touching production.
Q&A
Agency demands Admin?
Ask for minimal permission list mapped to official groups; full Admin is rarely needed.
One user for all packages?
Possible; prefer per-product users to shrink blast radius.
Read-only collaboration?
Fine for prep week; elevate temporarily for submit week, then revoke.
Relation to Google Cloud IAM?
Some APIs need Cloud roles; Console user ≠ Cloud Owner—audit both.
What does Goee need?
Define in handoff before @hagee66—package name and milestones.
Next steps
- Developer account setup
- Agency handoff checklist
- Google Play materials
- Signing handoff
- Apple mirror: ASC roles
Back to guide library · Official pages prevail · No approval guarantee.