Search
Getting Started
Feature guides
Integrations
Community support
A single Dreambase workspace can connect to multiple Supabase projects (Pro+ feature)
A single Dreambase workspace can now connect multiple Supabase projects, including projects from multiple different Supabase organizations. This is new since the previous docs were written, which assumed one workspace maps to one Supabase project.
Where it lives
Connectors → Manage Databases lists every connected Supabase project with a live healthy/unhealthy indicator per connection. The top nav also shows an aggregate connection-health badge (e.g. "1 of 1 healthy") so you can spot a broken connection at a glance.
Adding another project
Go to Connectors → Manage Databases.
Click + Add Database.
In the "New Supabase Connection" dialog, either connect another project from an org you've already authorized, or use Connect another org to authorize a brand-new Supabase organization.
Select the specific project within that org.
Why this matters
Agencies and multi-brand companies can bring every client's or brand's Supabase project into one Dreambase workspace instead of running separate workspaces per project.
Staging + production can both live in the same workspace, so dashboards, Skills, and Health report cards can be run against either without switching workspaces.
Tables from each connected project stay attributed to that project. When building a dashboard or Skill,
#table mentions and Skill Data Sources make clear which project a given table comes from.
Things to check
Each connected project gets its own Health report card (see the Health doc) — a security or performance issue in one project doesn't affect another's score.
Row-level access still follows each individual Supabase project's own auth/permissions; Dreambase does not merge auth across projects.
Pro+ feature
Creating additional workspaces beyond your default one requires Pro+.
A single Dreambase workspace can now connect multiple Supabase projects, including projects from multiple different Supabase organizations. This is new since the previous docs were written, which assumed one workspace maps to one Supabase project.
Where it lives
Connectors → Manage Databases lists every connected Supabase project with a live healthy/unhealthy indicator per connection. The top nav also shows an aggregate connection-health badge (e.g. "1 of 1 healthy") so you can spot a broken connection at a glance.
Adding another project
Go to Connectors → Manage Databases.
Click + Add Database.
In the "New Supabase Connection" dialog, either connect another project from an org you've already authorized, or use Connect another org to authorize a brand-new Supabase organization.
Select the specific project within that org.
Why this matters
Agencies and multi-brand companies can bring every client's or brand's Supabase project into one Dreambase workspace instead of running separate workspaces per project.
Staging + production can both live in the same workspace, so dashboards, Skills, and Health report cards can be run against either without switching workspaces.
Tables from each connected project stay attributed to that project. When building a dashboard or Skill,
#table mentions and Skill Data Sources make clear which project a given table comes from.
Things to check
Each connected project gets its own Health report card (see the Health doc) — a security or performance issue in one project doesn't affect another's score.
Row-level access still follows each individual Supabase project's own auth/permissions; Dreambase does not merge auth across projects.
Pro+ feature
Creating additional workspaces beyond your default one requires Pro+.