8 min read
Secure your Supabase account before you get locked out
Supabase has added backup passwords and recovery codes that reduce the risk of losing access to your project dashboard.
By Kenny TranWritten with AI assistance from the source
What has changed
On 13 November 2026, Supabase added new backup methods for signing in to the dashboard. The change applies to your Supabase account — the account that gives you access to projects, databases, authentication, storage and settings. It does not change how users sign in to the app you are building.
The update consists of separate features that complement each other:
- If you normally sign in through an OAuth provider, such as GitHub or ChatGPT, you can add a password for the email address associated with your Supabase account.
- If you use multi-factor authentication, MFA, you can create recovery codes that work when the authenticator app is unavailable.
The settings are under Account Security in the dashboard. Supabase describes the change in its changelog entry about backup sign-in methods.
OAuth means that another service confirms your identity to Supabase. When you choose to sign in with GitHub, you are sent to GitHub, approve the sign-in there and are then sent back to Supabase. This is convenient, but it also makes access dependent on your account with the provider working.
The backup password removes that dependency. If your GitHub account is locked, is no longer linked to the correct email address or is temporarily unavailable, you can instead sign in directly with your email address and password.
Recovery codes solve a different problem. MFA normally requires a code from an authenticator app after the usual sign-in. If your phone is lost or the app's data is not transferred to a new device, you can use a recovery code to complete verification.
It is important to understand the difference. A backup password does not replace the MFA step when MFA is enabled. Nor does a recovery code replace the usual sign-in. You need a working route through the entire chain.
Why this is a production issue
When Supabase is used for a prototype, the dashboard can feel like just another development tool. Once the app has paying users, the same account becomes an administrative key to production.
From the dashboard, authorised people can, among other things, change the database structure, read logs, manage API keys, adjust authentication and affect environments used by the app. Being locked out may not immediately stop an app that is already running, but it can make it difficult to diagnose and fix a problem.
Common causes of lost access are not particularly dramatic:
- A GitHub account is suspended after an automated security check.
- The email address held by the OAuth provider changes.
- A founder leaves the company and the company's accounts need to be transferred.
- A phone breaks before the authenticator app has been moved.
- A password manager or email inbox is temporarily unavailable.
- During an incident, someone discovers that recovery requires the same device that has been lost.
The problem is therefore not just the risk of a provider suffering a major outage. It is often that several dependencies are connected. If the Supabase sign-in, authenticator app, email and password manager can only be accessed from the same computer, you do not have a genuine backup method.
A good recovery plan therefore relies on independent routes. You should be able to lose access to one device or service without also losing everything needed to regain access.
This is also a matter of responsibility within the team. A shared Supabase account with a shared password makes it difficult to control who has access and what happens when someone leaves. Each person should use their own account with a role that matches their responsibilities. At the same time, not all owner access should depend on the same person.
How to add a backup password
Start by signing in to Supabase as usual. Open the account settings and go to Account Security. If the account has so far only used OAuth, you should be able to add a password linked to the account's email address.
Check the following before saving the password:
- Check which email address Supabase shows for the account.
- Make sure the address can still receive email and is managed by the correct person or company.
- Create a unique password that is not used for GitHub, Google, ChatGPT or any other service.
- Save the password in an established password manager, not in the project's documentation or source code.
- Document that email and password are a backup method so that it is not forgotten during an incident.
A long, random password generated by the password manager is better than something designed to be easy to remember. The purpose is not to enter the password frequently, but to have it available when OAuth sign-in does not work.
Then test the backup method without ending the session you are already using. Open a private browser window, go to Supabase and try to sign in with your email address and password. This lets you check that the password belongs to the correct account without risking your active session.
After signing in, verify that the correct organisations and projects are shown. A successful sign-in is not enough if it leads to another Supabase account that happens to use a similar email address.
The backup password must also be treated as an active sign-in method. This means you should change it if the password manager is compromised or if someone who had access leaves the team. Otherwise, a backup method that is never maintained can become both unusable and insecure.
How to use and store recovery codes
MFA adds a verification step beyond the usual sign-in. Supabase uses time-based one-time codes generated by an authenticator app. The code changes continuously and shows that you have access to the registered authenticator.
If MFA is not already enabled, you can configure it under Account Security. Be aware that other active sessions may end when the feature is enabled. Make the change when you have time to sign in again and check that everything works.
When the recovery codes are displayed, save them immediately. Supabase shows them during configuration, and each code is intended for one-time use.
Suitable places to store them include:
- A protected note in the company's password manager.
- A separate, encrypted copy that can be accessed if your usual device is lost.
- A physical copy kept securely, if company procedures allow it.
Do not put the codes in:
- A Git repository, even if it is private.
- Slack, email or a document with broad access.
- An unencrypted file in the project folder.
- A screenshot that is automatically synchronised to a standard photo library.
- The same phone that holds the authenticator app, if there is no separate copy.
The dashboard shows whether any codes remain and lets you create a new set. When you generate new codes, the old ones stop working. Do this if a code has been used, if the storage location may have been exposed or if you are unsure which copies still exist.
Do not test a recovery code simply by entering it and then continuing to use the same list without documenting it. Because the code is used up, it must be marked as used or replaced by generating new codes.
A recovery code is also not an everyday alternative to the authenticator app. It is intended for recovery. If the authenticator has been lost, after signing in you should register a new MFA method, remove the old one and make sure new recovery codes are stored securely.
Check the whole process before you need it
Backup sign-in only helps if you have tested the entire process. Carry out the check under normal conditions rather than when the database already has a problem.
- Check that the account's email address is current and accessible.
- Add a unique backup password if you normally use OAuth.
- Save the password in a password manager with appropriate access controls.
- Enable MFA for the Supabase account.
- Save the recovery codes outside the authenticator app.
- Keep a separate, protected copy that does not depend on the same device.
- Test the backup password in a private browser window.
- Check that signing in leads to the correct organisation and project.
- Document who may use the recovery details and in which situations.
- Review access when someone joins, changes role or leaves the company.
Also write a short procedure for what should happen if someone is locked out. It does not need to be complicated. What matters is that the team knows where the codes are, who may use them, how identity should be confirmed and which details should be changed after recovery.
At the same time, avoid making recovery dependent on a single founder. Access should not be distributed more widely than necessary, but there should be a controlled way for the company to manage production when the usual owner is ill, away or no longer available.
Supabase's change makes it easier to create such a route, but the settings must be enabled and maintained before they are needed. When preparing production for paying customers, working backup sign-in should be part of the same checks as database permissions, payments and operations.
Source: Supabase changelog GitHub
Want to know what your build would take?
Three questions, then you get a clickable sketch for free.