Your agency has asked for access to Google Play. You don't need to share your password for it. Google Play lets you add them with their own login, choose exactly what they can do, and remove them when the project ends. These are the clicks, checked against Google Play's own help pages in October 2026.
Which role to choose
Pick the narrowest role that lets your agency do the work. Release manager is usually the right one.
| Role | What it allows | For an agency |
|---|---|---|
| Release manager | Creates and rolls out releases and manages the store listing for the chosen app. | Usually the right one |
| Developer | Testing tracks and app content, without releasing to production. | If the work needs it |
| Admin | Every permission on the chosen app. | If the work needs it |
Add your agency to Google Play
- Open Play Console and go to Users and permissions.
- Click Invite new users and enter your agency's email address.
- On the App permissions tab, click Add app, choose your app and click Apply.
- Turn on the permissions for Release manager, then click Invite user.
How you both know it worked
Google Play emails your agency an invitation from google.com. Once they accept it, they show in your Google Play account's list of people with access, where you can see or change their role at any time.
Remove access when the project ends
- Open Users and permissions in Play Console.
- Find your agency's email address, open Manage and click Remove user.
Do you have to share your password?
No. Every step above uses Google Play's own invite, so your agency signs in with their own account, your two-step verification stays on, and anything they change is recorded under their name. How to give a developer access without sharing your password covers the other accounts agencies usually ask for.
Doing this for every client?
Agencies can send each client one Get Set Keys link instead of a page like this. It walks the client through Google Play and the other platforms the project needs, and checks that each step is done.