Your agency has asked for access to RevenueCat. You don't need to share your password for it. RevenueCat 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 RevenueCat's own help pages in November 2026.
Which role to choose
Pick the narrowest role that lets your agency do the work. Developer is usually the right one.
| Role | What it allows | For an agency |
|---|---|---|
| Developer | Manages app settings, products, offerings, paywalls and integrations. Cannot see revenue totals in Charts or create secret API keys. | Usually the right one |
| Administrator | Everything in the project except billing, including secret API keys and inviting other collaborators. | If the work needs it |
| Operations | Developer, Growth and Customer Support together, revenue data included. Cannot manage API keys or collaborators. | If the work needs it |
| Growth | Views nearly everything and edits paywalls, offerings, entitlements and products. Cannot change app settings or integrations. | If the work needs it |
Add your agency to RevenueCat
- Sign in to the RevenueCat dashboard and open your project.
- Go to Project settings, select the Collaborators tab and click Invite.
- Add your agency's email address, select Developer as the permission level and send the invite.
Only the project owner or an Administrator can invite, and collaborators are free on every plan. Access is per project, so repeat this for each project your agency works on.
How you both know it worked
RevenueCat emails your agency an invitation from revenuecat.com. Once they accept it, they show in your RevenueCat account's list of people with access, where you can see or change their role at any time.
Remove access when the project ends
- In the RevenueCat dashboard, open your project, go to Project settings and select the Collaborators tab.
- In the Actions column next to your agency's email address, click the three dots (...) and remove the collaborator.
- In Project settings, open API keys and revoke any secret API keys your agency created.
Do you have to share your password?
No. Every step above uses RevenueCat'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 GetSetKeys link instead of a page like this. It walks the client through RevenueCat and the other platforms the project needs, and checks that each step is done.