Your agency has asked for access to Expo. You don't need to share your password for it. Expo 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 Expo'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 | Creates projects, makes builds, releases updates and manages credentials. | Usually the right one |
| Release Manager | Developer, plus protected resources such as protected update channels and protected credentials. | If the work needs it |
| Admin | Release Manager, plus most account settings: paid services, other members' roles and access tokens. | If the work needs it |
Add your agency to Expo
Open Members If you belong to more than one account, check that your organization is the account shown.
- Sign in at expo.dev. Select your username in the navigation menu and pick your organization under Organizations.
- Open Members under Organization settings and click Invite.
- Enter your agency's email address, select the Developer role and send the invitation.
Only an Owner or Admin can invite, and only Organization accounts have members. If your projects are in a personal account, use Convert your account into an organization in User settings first.
How you both know it worked
Expo emails your agency an invitation from expo.dev. Once they accept it, they show in your Expo 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 Members under Organization settings in the Expo dashboard.
- Next to your agency's account, click the three-dotted menu icon, then Remove member.
- On the Access tokens page, delete any robot users or tokens your agency created for your organization.
Do you have to share your password?
No. Every step above uses Expo'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 Expo and the other platforms the project needs, and checks that each step is done.