The Data tab of a table is a spreadsheet-like view of its rows. Use it to look at data, fix a value, add a test row or clear out mistakes. It acts with Studio’s own authority, so it sees every row regardless of your access rules. That makes it ideal for support work, and a reason to restrict who can open Studio.

​
In Studio

Data → Data, pick a table in the sidebar (or Open a table in a new tab to keep several open).

​
Browse

Rows load 50 at a time. Use First page, Previous page, Next page, and Reload rows when the data may have changed. The column headers show the types.

​
Filter and sort

  • Filter rows: choose a Column, a Condition and a Value, and add more conditions to narrow further.
  • Sort rows: choose a column and direction.
Filters here are for looking, like eq / gt / like in your app, but evaluated with operator authority, not a user’s.

​
Add and edit

  • Add row opens a form with an input per column, honouring each column’s type: a toggle for yes/no, a picker for choices, a date picker, a JSON editor. Required columns are marked Required; empty optional ones show Not set.
  • Click a row to edit it. Delete removes it after confirmation.
Writes made here run your normal pipeline, so the record’s events fire and realtime is told, just as if the app had written it. Use the import wizard’s switch if you want imports to stay quiet (Import and export).

​
Export

Export table downloads every row as a file (CSV or JSON).

​
Seeding development data

A script that fills development so the team has something to work with, using a development secret key:
For many rows use import, which batches.

​
Tips

  • Treat the production table editor like a live production shell: change a value only when you know why, and prefer a flow or a fix in the app.
  • If a row doesn’t appear in your app but you can see it here, your access rule is hiding it. Check Access.
  • Large tables paginate; use filters rather than scrolling.

SQL editor

When you need queries.

Import and export

Many rows at once.