You've decided to get help with your app. Then comes the awkward moment: the developer asks for access. Many founders send their main password over WhatsApp, or paste a Stripe secret key into an email. It works, but it hands a stranger the keys to everything, with no record of what they did and no easy way to take it back.
There's a better way, and it takes about the same time. Below: what to send first, how to give access without sharing passwords on GitHub, Supabase, Firebase and Stripe, what never to send, and how to clean up when the job is done.
Start with a one-page brief
A developer can tell you a lot before touching anything. Send one page with:
- What the app does, in two sentences, and who pays for it.
- The live link and a test login. Make a separate test account; don't share your own.
- The 3 to 5 flows that make or keep money: sign up, pay, use the main feature, cancel. Mark the ones that break.
- What changed just before it broke, if you know.
- The services the app uses: GitHub, Supabase or Firebase, Stripe, hosting, email. Names only, no keys.
- What "done" means to you, and your deadline.
Most first answers, like "is this a fix or a rebuild?" and "how big is this?", come from that page plus a look at the code. The fix-or-rebuild self-check helps you fill it in.
Invite people, don't share passwords
Every service below lets you invite a developer with their own login. You decide what they can do, you can see what they changed, and you can remove them in one click. Your own password and two-step login stay yours.
GitHub (the code)
In your repository, go to Settings → Collaborators → Add people and enter the developer's GitHub username. One thing to know: on a repository in a personal account, a collaborator can always push changes. GitHub's docs say collaborators "can't have read-only access" there. They can't delete the repository, change who can see it or invite others; those stay with you.
If you want someone to only read the code at first, put the repository in a GitHub organization. There you choose a role per person, from Read up to Admin.
Supabase (database and logins)
In your organization's team settings, invite the developer by email (the invite link expires after 24 hours). Pick Developer: Supabase describes it as "read-only access to organization resources, full content access to project resources", and a Developer can't change project settings. Keep Owner and Administrator for yourself.
Watch out on the Free and Pro plans: the role covers every project in the organization, because Read-Only and per-project roles are only on the Team and Enterprise plans. If one organization holds several apps, the developer can see all of them.
Firebase
Go to Project settings → Users and permissions → Add member. Editor is enough for almost all development work. Owner can also manage who has access, set up billing and delete the project, so keep that role for yourself. Viewer is read-only, which is fine for a first look.
Stripe (payments)
Stripe has a role made for this. A Sandbox User can create their own sandbox to build and test your checkout in, and in Stripe's words "can't view or make changes to anything in your live account". Start there.
The Developer role is a big step up: it "can create secret keys, which grant access to almost all API resources", and it can refund payments too. If live setup needs doing, give that role for the day it's needed, then switch it back.
Better still, keep the live secret key out of the developer's hands completely. They tell you the name of the setting your hosting needs, and you paste the live key into your hosting dashboard yourself. The key goes from Stripe to your hosting and nowhere else.
Hosting and your domain
On hosting like Netlify or Vercel, invite the developer to your team if your plan allows it. If it doesn't, keep the login and change settings yourself when they ask. Keep the login for your domain registrar to yourself either way. If the domain needs new DNS records, the developer sends you the exact records and you add them. It takes five minutes, and nobody else can move your domain.
What never to send
- Your main email password. Whoever has it can reset every other account you own.
- Two-step login codes. No developer needs them. If someone asks for one, stop and check who you're talking to.
- Live secret keys in a chat or email. That means keys starting with
sk_live_(Stripe) orsb_secret_, or the service_role key (Supabase). Chats and inboxes are kept for years and synced to every phone. If a key really has to move, use the share feature of a password manager and replace the key when the job is done. - A copy of your real customer data. A developer can almost always work with test data. If they really need real personal data, the GDPR expects a written contract with anyone who handles personal data for you (Article 28, usually called a data processing agreement). That's a technical note, not legal advice.
When the job is done: a 10-minute clean-up
- Remove access on GitHub, Supabase, Firebase, Stripe and your hosting once the work is over. For the full account check (two-step login, recovery codes, domain lock), see lock down the accounts that run your app.
- Replace every key that left a dashboard. Make a new one, update it in your hosting, then delete the old one. Stripe calls this rolling a key.
- Check the code is in your GitHub, not only on the developer's laptop. The latest change should be there.
- Ask for a short handover note: what changed, which settings matter, and what's still open.
- Write down where everything lives (code, database, payments, hosting, domain, email) in one place you own.
Before real users pay, the launch-ready checklist covers what to test.
Need a developer for your app?
I'm Marc de Ruijter, a Dutch full-stack developer with 25+ years in IT, working remotely for clients in Europe. I've shipped 20+ products alone, with Stripe, Supabase, Firebase, Neon and AI APIs. Send me your one-page brief and I'll tell you in plain words what I see, which access I'd need (the smallest roles that do the job) and what the work would take. In Dutch or English.