Your agency has asked for access to Google Cloud. You don't need to share your password for it. Google Cloud 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 Cloud's own help pages in October 2026.
Which role to choose
Pick the narrowest role that lets your agency do the work. Editor is usually the right one.
| Role | What it allows | For an agency |
|---|---|---|
| Editor | Creates, changes and deletes most resources in the project. Cannot manage access or billing. | Usually the right one |
| Viewer | Sees resources and data without changing anything. | If the work needs it |
| Owner | Nearly everything, including access and deleting the project. | If the work needs it |
Add your agency to Google Cloud
- In the Google Cloud console, go to IAM & Admin, then IAM, and select your project.
- Click Grant Access and enter your agency's email address.
- Click Select a role, choose Editor, then click Save.
How you both know it worked
Google Cloud emails your agency an invitation from google.com. Once they accept it, they show in your Google Cloud account's list of people with access, where you can see or change their role at any time.
Remove access when the project ends
- Go to IAM & Admin, then IAM, for your project.
- In the row for your agency's email address, click Edit principal, click Delete next to each role, then click Save.
Do you have to share your password?
No. Every step above uses Google Cloud'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 Cloud and the other platforms the project needs, and checks that each step is done.