# Connect Supabase

> Authorize Supabase, choose the correct project, review database changes and verify that your mobile app saves data and keeps accounts separate.

Canonical: https://www.rnblocks.dev/docs/connectors/supabase
Updated: 2026-10-07

Use Supabase when your app needs user accounts, shared data or storage. Connecting your Supabase account, selecting a project and applying database changes are separate steps.

## Before you start

- An app in Studio and a Supabase account. Create the provider account yourself if you do not have one.
- Access to the Supabase organization and project you intend to use.
- A description of what the app should save and who should be allowed to see it.

## New to Supabase? Start here

Section: https://www.rnblocks.dev/docs/connectors/supabase#first-time

Your RNBlocks account and Supabase account can use different email addresses. Sign in to the Supabase account that owns, or has access to, the organization you want to use.

1. **Create your Supabase account** — Open the Supabase dashboard and complete sign-up and any email verification yourself. Keep your original RNBlocks tab open.

2. **Check or create your organization** — Use your existing organization if it is the right home for the app. If Supabase asks you to create one, enter a name, select the appropriate type and review the plan before creating it. You do not need a second organization just to connect RNBlocks.

3. **Start the connection from RNBlocks** — After account setup, return to your app in the same browser. Open **App options (+) → Supabase**, then start **Connect Supabase**. Review the selected organization and requested access on Supabase’s authorization page.

4. **Choose a project after authorization** — Return to RNBlocks and check the connection status. Choose an existing project, or use the prepared backend’s **Set up database** action to review a new project. Creating an organization alone does not connect your app or create its tables.

| Term | What it means |
| --- | --- |
| Account | Your own Supabase sign-in. This is separate from the sign-in people will use inside your finished app. |
| Organization | A group of projects with team access and billing settings. A personal app can use a personal organization. |
| Project | The backend for an app: its database, authentication and storage. Choose the correct project before reviewing changes. |

### Figure: Your organization in Supabase

The organization form asks for Name, Type and Plan. Organizations group projects and control team access and billing.

1. Reuse the intended organization if you already have one.
2. Review the plan before selecting Create organization.
3. Return to RNBlocks to authorize access and choose the project for your app.

Supabase dashboard, captured October 7, 2026. Empty form; nothing was submitted. Interface and plan options may change.

[Supabase dashboard](https://supabase.com/dashboard/new)

- [Open the Supabase dashboard](https://supabase.com/dashboard)
- [Supabase organization access](https://supabase.com/docs/guides/platform/access-control)

## Sign-in and preview support

Section: https://www.rnblocks.dev/docs/connectors/supabase#sign-in-and-preview

Start with email and password for accounts in your app. Connecting your own Supabase account to Studio is a separate step: it lets Studio work with the project you select, rather than signing your app’s users in.

| Feature | What to expect |
| --- | --- |
| Email and password | Supported for app sign-in in Web preview and Expo Go. Ask Studio to include sign-in, saved sessions and sign-out. New-account email confirmation follows your Supabase project settings. |
| Google and Apple sign-in | Not yet verified end to end in RNBlocks previews. Use email and password while building. Social sign-in needs separate provider setup and callback configuration; test the mobile flow in a development build before offering it to users. |
| Private file uploads | Require a Storage bucket, access rules and upload/download code in your app. Connecting Supabase alone does not create an upload feature. Check uploads and file access with two accounts before sharing the app. |
| Live database updates | Require Realtime enabled for the intended tables, access rules and a compatible app connection. Realtime is not yet generally available through RNBlocks’ standard preview connection; do not assume a connected project enables live updates. |

> **Test the feature, not just the connection**
> A successful connection or configuration check does not prove your app’s complete feature works. Test the actual sign-in, upload or update flow in each preview you intend to use. File selection, upload progress and recovery also depend on the app code.

- [Supabase email and password sign-in](https://supabase.com/docs/guides/auth/passwords)
- [Expo OAuth development-build requirements](https://docs.expo.dev/guides/authentication/)

## Authorize your account

Section: https://www.rnblocks.dev/docs/connectors/supabase#authorize

1. **Ask for the data feature** — For example: “Let people sign in and save their favorite places. Each person should only see their own saved places.” Use the **Connect Supabase** request, or open **App options (+) → Supabase**.

2. **Complete Supabase sign-in** — Supabase opens in the same tab. Sign in, choose the intended organization and review the requested access. If email verification opens another browser, finish verification there, then continue in the browser where you started.

3. **Return to Studio** — After authorization, RNBlocks returns to the same app. Choose a project if prompted, or check **App options (+) → Supabase**. You do not paste a project URL, database password or secret key into Studio chat to complete this flow.

### Figure: Connect your Supabase account

Open App options (+) → Supabase, use Connect with Supabase and authorize in the separate provider page. Back in Studio, Database setup opens the project picker.

1. **App options** — The actual App options menu above the + button. It contains separate Supabase, Connectors and App memory actions.

2. **Authorize** — The actual Connect Supabase dialog with a Connect with Supabase button. Authorization opens separately at Supabase.

3. **Return to Studio** — Illustrative Supabase Connection state after account authorization, before selecting a project. Database setup opens the project picker.

4. **Choose a project** — The actual database project picker with Create a new project and an illustrative Aria project under Example team.

1. Choose Supabase from App options (+). It is separate from the API-key connector catalogue.
2. Complete authorization at Supabase, then return to Studio. The provider authorization page is not pictured here.
3. Open Database setup to select your project and review the proposed changes.

Actual RNBlocks setup screens, with an illustrative account-connected state and example Aria project.


## Choose the project and review setup

Section: https://www.rnblocks.dev/docs/connectors/supabase#project

1. **Prepare the backend in the conversation** — Explain the accounts, records and access rules you need. If **Database setup** says to prepare the backend in chat, finish that step before choosing a target.

2. **Open Database setup** — Go to **App options (+) → Supabase → Database setup**. Choose the existing project that belongs to this app. For a new project, select **Create a new project** and review **Project name**, **Organization** and **Region**.

3. **Review the exact changes** — Select **Review setup** when creating a project. Open the saved review in the conversation, check the target and proposed changes, then approve only the setup you intend. Supabase project costs follow your organization’s plan and are separate from RNBlocks credits.

4. **Check the result** — Wait for the setup outcome. If work was interrupted, use **Check status** or reopen the existing review before starting again. Approval alone does not establish that all changes finished.

### Figure: Choose or create your app’s project

Database setup offers an existing Aria project or Create a new project. The new-project form asks for Project name, Organization and Region, then offers Review setup.

1. **Choose a project** — The database project picker shows Create a new project and an illustrative Aria project.

2. **New project** — The actual new-project form shows Project name, Organization, Region and Review setup. Values are examples; no project was created.

1. Select the project that belongs to this app, or choose Create a new project.
2. For a new project, check its name, organization and region.
3. Review setup prepares a review. Read and approve the intended changes in your conversation before they run.

Actual project picker and new-project form with illustrative Aria and Example team values.


## Prove that the app saves correctly

Section: https://www.rnblocks.dev/docs/connectors/supabase#test

- Open the iOS or Android preview, sign in with a test account and save a record.
- Close and reopen the app. Confirm the saved record returns and that sign-out behaves as expected.
- For private data, use a second test account and confirm it cannot see the first account’s records.
- Check the app’s email-confirmation and password-recovery journeys if it uses them. A connected database does not finish those user flows automatically.

> **Protect private records**
> [Supabase Row Level Security](https://supabase.com/docs/guides/database/postgres/row-level-security) controls which rows a user can reach. Ask Studio to check the app’s access rules alongside its save and reload behavior.


## If setup stops

Section: https://www.rnblocks.dev/docs/connectors/supabase#recovery

| Problem | Next step |
| --- | --- |
| Couldn’t verify this connection attempt | Return to the original RNBlocks tab in the same browser and check App options → Supabase. If it is already connected, continue with project selection; otherwise start Connect Supabase again. Keep the existing Supabase account and organization; do not recreate them. If it happens again, report the app name, time and browser to RNBlocks support. |
| Connection request is no longer active | Start a new connection from the original app. A long account setup or a newer connection request can make an earlier authorization attempt unusable. |
| Connection save could not be confirmed | Open App options → Supabase and check the current status before reconnecting. |
| The authorization page did not open | Allow the connection tab to open, then use the connection button again. Complete sign-in in the provider page. |
| Your account is connected but no project is selected | Use Database setup. You do not need to reconnect just to choose a project. |
| The intended project is missing | Check the signed-in Supabase account, organization and access. Do not create a replacement project merely because the list could not load. |
| A project quota or billing message | Resolve it in the intended Supabase organization or choose another project you are authorized to use. Project creation is subject to provider limits. |
| Setup was interrupted | Reopen the saved review and check its status. Tell Studio the outcome before requesting another setup attempt. |
| Sign-in works but saving fails | Tell Studio which record and action failed. Ask it to check the connected project, table access and user-specific policies. |


## Disconnect without deleting the project

Section: https://www.rnblocks.dev/docs/connectors/supabase#disconnect

Open **App options (+) → Supabase → Disconnect**, then confirm **Yes, disconnect**. This removes the app’s saved RNBlocks connection. Your Supabase project and its data remain with Supabase; reconnecting requires authorization and selecting the project again.

Removing the app connection does not cancel Supabase billing or revoke the account’s provider-side authorization. To remove that authorization too, review RNBlocks under Supabase’s Authorized Apps. Check other apps before revoking a shared authorization.


## Continue

- [Connect services](https://www.rnblocks.dev/docs/connectors)
- [Preview and test](https://www.rnblocks.dev/docs/previewing-screens)
- [Prepare for publishing](https://www.rnblocks.dev/docs/publishing)

## Official references

- [Supabase access control](https://supabase.com/docs/guides/platform/access-control)
- [Supabase OAuth integrations](https://supabase.com/docs/guides/integrations/build-a-supabase-oauth-integration)
- [Supabase Row Level Security](https://supabase.com/docs/guides/database/postgres/row-level-security)