Table editor
Database › Tables is a spreadsheet-style editor for the project database. It's built for people who will paste data in from Excel, as well as for developers.
Create a table
- Open the project, then Database › Tables, and select New table.
- Name the table and add columns. The type picker offers common types; any valid Postgres type is accepted.
- Pick a row-level security template. New tables always get row-level security turned on, with one of: Everyone with app access can read, Rows belong to the creator, Editors can write, A role can read and change every row, or An Entra group can read. See Row-level security.
- Create. The table appears in the list with an RLS on badge showing how many policies it has.
Column types in the picker
| Label | Postgres type |
|---|---|
| Text | text |
| Integer (int8) | int8 |
| Integer (int4) | int4 |
| Decimal (numeric) | numeric |
| Float (float8) | float8 |
| Boolean | bool |
| Date | date |
| Date & time (timestamptz) | timestamptz |
| UUID | uuid |
| JSON (jsonb) | jsonb |
| Text list (text[]) | text[] |
Work with rows
- Edit inline: double-click a cell, change it, press Enter.
- Add and delete rows from the toolbar.
- Sort and page on the server, 100 rows per page.
- Add, change or drop columns with the column tools.
- Toggle RLS per table. A table with RLS off shows an amber open-lock icon in the list.
The Studio works as the project's owner role, so you see every row regardless of policies. Your app's users see rows through row-level security.
Import and export CSV
- Import CSV: CSV headers must match column names. Unknown columns are ignored and listed after the import. If a row fails, the import stops and says how many rows were imported.
- Export CSV: downloads every row of the table.
Who can edit
The owner, people with the developer app role, Org Admins, and Delegated Admins in scope. Auditors and others with read-only access can browse tables but not change them. All changes are audited.
Prefer migrations for structure
The table editor is ideal for exploring and fixing data. For schema changes you want to keep, also commit them as migrations in db/migrations/, so a fresh environment or a teammate's agent can rebuild the same schema.
Was this page helpful?