States
Understand the database stages
The `Database` tab starts with an overview and then moves through three practical states.
Overview
The tab first shows whether an account or project is already connected and which action is available next.
No Supabase account connected
Flutty asks you to connect a Supabase account.
Account connected, but no project linked yet
You can choose an existing Supabase project or create a new one from inside Flutty.
Supabase project linked
The workspace can show connection details, table explorer data, and auth-user information.
Setup
Link an existing project or create a new one
Flutty supports both paths because teams do not all start from the same backend situation.
- 01
Connect the Supabase account
The tab starts the account OAuth flow and returns you to the same workspace.
- 02
Choose the right backend strategy
Link an existing Supabase project if one already owns the data, or create a new project if the workspace still needs a backend home.
- 03
Review creation defaults when creating a new project
Flutty pre-fills the Supabase project name from the Flutty project title, suggests an organization when available, and selects a region group from your locale.
- 04
Bind the project to the active Flutty project
After that link is saved, the workspace treats the database as part of the same product context.
Explorer
Explore what was connected
Once a Supabase project is linked, the tab becomes an inspection surface instead of a setup prompt.
Connection summary
Review the bound project, region, and connector state without leaving the workspace.
Table explorer
Browse tables and inspect table details when you need to confirm schema shape.
Auth users
Review authentication users from the linked Supabase project in the same tab.
Refresh and disconnect actions
Refresh data when the backend changed recently, or disconnect the project if the current binding is no longer correct.
Boundary
Know what the tab does not depend on
The `Database` tab is not the same kind of surface as preview, `Code`, or `Terminal`.
Supabase account, project, table, and auth-user data come from the connector APIs rather than from the preview server.
Opening the tab can still participate in the workspace preparation flow, so do not treat it as proof that the runtime is healthy.
It is connector-driven rather than preview-driven.
It is best used for backend setup and inspection, not for judging frontend behavior.