Expo and React Native Apps: Which Accounts Your Business Should Own
Short answer: An Expo app depends on more accounts than most owners realise: the Expo organisation where the project and its EAS builds live, the Apple Developer and Google Play accounts, the signing credentials and push notification keys stored in EAS, any error tracking or analytics service, and the Git repository with the source code. Your business should be the owner of each, with the developer invited as a member. If the project currently sits under a freelancer's own Expo login, create a company organisation, add yourself as owner, and transfer the project there. Then confirm you can download the signing credentials and that the repository is in an organisation you control.
Why this matters for an Expo app in particular
Expo's EAS services do a lot of quiet work: they build the app in the cloud, store iOS certificates and Android keystores, and can submit builds to the stores. Convenient, but it means critical pieces live in an Expo account. If that account belongs to a freelancer who later becomes unreachable, you may still own the store listings and yet be unable to ship an update, because the build pipeline and credentials are somewhere you cannot log in.
The account map
Work through this table with your developer. For each row, write down the account owner, the login email, and who else has access.
| Account | What it holds | Who should own it |
|---|---|---|
| Expo organisation | Project, EAS builds, updates, stored credentials, environment variables | Your business |
| Apple Developer Program | App Store listing, certificates, push keys, TestFlight | Your business, enrolled as an organisation |
| Google Play Console | Play listing, app signing key (with Play App Signing), testing tracks | Your business |
| Firebase project | Android push (FCM), possibly analytics or crash reporting | Your business |
| Error tracking (for example Sentry) | Crash reports, release health | Your business |
| Analytics tool | Usage data | Your business |
| Git repository host | Source code, history | Your business organisation |
| Backend and database | API, user data | Your business |
| Domain and email | Links, password reset emails, store contact address | Your business |
Every row where the answer is someone outside the company goes on your to-do list.
The Expo organisation
Expo has personal accounts and organisations. Organisations support multiple members with roles such as owner, admin, developer and viewer, as explained in the Expo account types documentation.
Setting it up
- Create an Expo account with a business email address that does not depend on one person, for example apps@yourcompany.com, with two-factor authentication.
- Create an organisation named after your business.
- Make that account the owner. Add a second trusted colleague as owner or admin, so you are not locked out if one person leaves.
- Invite your developer with the developer or admin role, depending on what they need.
Transferring an existing project
When the project was created under the freelancer's own username, Expo allows projects to be transferred to another account or organisation from the project settings. Before transferring, agree a time with the developer, because:
- The
ownerfield in the app configuration (app.jsonorapp.config.js) should be updated to the organisation's name. - Build profiles, environment variables and secrets need checking after the move.
- Over-the-air update channels should be tested with a preview build.
Ask the developer to do the transfer while you watch, and then run a fresh build under the organisation to confirm everything works.
Store accounts
Apple
The App Store listing belongs to whichever Apple Developer account published it. Enrol your business as an organisation, which needs a D-U-N-S number, and invite the developer through App Store Connect users and access with an appropriate role. If the app is currently published under the developer's account, Apple supports app transfers between developer accounts, subject to conditions.
Create the Play Console account under the business. Grant the developer access under Users and permissions, limited to release and testing tasks. Use Play App Signing so Google holds the app signing key, and the upload key used by EAS can be reset if it is lost. Android's app signing guide explains the difference between the two keys.
Push credentials
Push notifications break quietly when credentials disappear.
- iOS: an APNs key from your Apple Developer account. EAS can generate and store it, but the key itself belongs to your Apple account.
- Android: Firebase Cloud Messaging credentials, which come from a Firebase project. That Firebase project belongs under a company Google login as well.
After the Expo organisation is in place, open the credentials section for the project and check which push credentials are attached and where they came from.
Signing credentials
EAS can manage iOS distribution certificates and provisioning profiles and the Android upload keystore. Ask your developer to:
- Confirm whether credentials are managed by EAS or supplied locally.
- Show you how to download the Android keystore and iOS credentials from EAS.
- Keep a backup copy in the company vault where other shared secrets live.
You may never need them, but if you switch developers or tools, having them saves days.
Monitoring and analytics
Error tracking and analytics services often get set up with the developer's own login during the build because it is quick. Each has an organisation feature; move the project into an organisation you own, leave the developer's access in place, and check that the DSN or keys used in the app point to that project.
Repository
The source code should live in a GitHub, GitLab or Bitbucket organisation the company controls, with the developer added as a collaborator. Should the repo still sit under their own username, ask them to transfer the repository to your organisation. Check that the transfer includes the full history, not a zip of the latest files, and that the build configuration (eas.json) is in it.
A handover checklist
- [ ] Expo organisation owned by the business, with two owners or admins from the business
- [ ] Project transferred and a build completed under the organisation
- [ ] Apple and Google accounts registered to the company, developer invited
- [ ] Push credentials traced to business-owned Apple and Firebase accounts
- [ ] Signing credentials downloaded and kept in the company vault
- [ ] Monitoring and analytics projects moved to business organisations
- [ ] Repository in the business's organisation, with full history
- [ ] Backend, database and domain accounts listed with owners
- [ ] Access review date set in the calendar, every six months
FAQ
Does the developer lose access when we transfer the project?
Not if you invite them to the organisation first. Their day-to-day work carries on; only the top-level ownership changes hands.
Do we need to pay for Expo to have an organisation?
Organisations are available on Expo's plans; build and update usage limits depend on the plan. Check Expo's current pricing page.
What if our developer refuses to transfer?
Review your contract for ownership terms. Often the store listings and domain are already registered to you, which gives you leverage; a new developer can rebuild credentials if needed, though it takes time.
Can we use robot accounts for CI instead of personal logins?
Yes. Expo supports access tokens and robot users for automated builds, which avoids tying pipelines to one person's login.
If you want your Expo app's accounts audited and moved under your business without breaking builds, send us a message and we will plan the handover.