SoupCMS does not ask you to migrate content into a proprietary store. You point it at your Supabase project, pick what editors can touch, and ship a polished UI.

Before you start

An active Supabase project with the tables your clients will edit
Permission to create API keys (or a key scoped for CMS use)
A SoupCMS account

1. Sign in to SoupCMS

Open app.soupcms.io and start a trial. You’ll create or join an organization that owns your CMS workspaces.

2. Add the Supabase connection

In the dashboard, add a new project connection. You’ll need your Supabase project URL and a key with enough access for the tables you expose. Prefer the least privilege that still lets editors do their jobs—especially on production data.

3. Configure what clients see

Pick tables, labels, and view types (table, kanban, and more). Hide internal columns, set friendly names, and lock down destructive actions when clients should only update content—not schema.

4. Invite your clients

Add users with role-based access. They log into SoupCMS, not the Supabase dashboard, so they can’t accidentally change RLS policies, run SQL, or browse tables you never meant to share.

Security notes

Connections use encrypted transport; see our security page
Your data stays in your Supabase project
Rotate keys if a collaborator leaves or a key is exposed

Next steps

Compare workflows with Supabase Studio, or read how teams hand off content to clients.