Your agency has asked for access to Firebase. You don't need to share your password for it. Firebase 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 Firebase'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 | Works on every Firebase product. Cannot manage members or billing. Some Cloud Functions deploys need extra roles in Google Cloud. | Usually the right one |
| Firebase Admin | Full access to Firebase products only. Deploying Cloud Functions needs more than this role. | If the work needs it |
| Owner | Everything, including members and billing. | If the work needs it |
Add your agency to Firebase
- In the Firebase console, open your project, then Settings (the gear icon), then Users and permissions.
- Click Add member and enter your agency's email address.
- Choose the Editor role, then click Add.
How you both know it worked
Firebase emails your agency an invitation from google.com. Once they accept it, they show in your Firebase 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 for your project in the Firebase console.
- Tick the box next to your agency's email address and click Remove member.
Do you have to share your password?
No. Every step above uses Firebase'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 Firebase and the other platforms the project needs, and checks that each step is done.