Your data
Everything your app saves, like orders, bookings, and customers, lives in your app's database, and it is yours from the first minute. The Database page opens on your data and has a second view, Structure, for how it is organized.
Data
Think of each table as a spreadsheet: one table for orders, one for customers, with a row for each order and a column for each detail. Tables open in tabs, so you can keep orders open next to customers and compare. Each tab has its own search across every column, filters such as "status is paid" or "total > 100", sorting, and hidden columns, and your tabs are still there next time.
This is the real data your live app uses, so editing is careful. Double-click a cell, or open a row to see every detail at once. Your changes wait in the tab until you press Apply, which saves all of them or none of them. If a value is not allowed, that field says why and nothing is saved. Each row's History shows who changed it and what it said before, and a person's row in the users table shows their whole story: their sign-ins, account changes, and edits to anything connected to them. The whole project's history is on Activity, under Run.
Structure
A map of your tables and how they connect. Each box is a table, and each line inside it says in plain words what that column holds: Text, Number, Date, ID, or Links to customers. A link connects a row to a row in another table, like an order pointing at the customer who placed it, and each line between boxes is one link. The ID is each row's unique value, the one that links from other tables point at. Hover a column to see its technical type.
Choice lists
Some columns accept only a fixed set of values, like an order status that can only be pending, paid, or shipped. That column says "Choice: pending, paid, shipped", and every list is shown under the map. Use one whenever a column should only ever hold a few known values.
Changing how your data is organized
To add a table or a column, describe it in the Insight panel on the Database page: "add a notes column to orders", "create a coupons table with a code and an expiry date". Insight writes the change and shows it on a card for you to apply. Afterwards the panel tells you what changed: tables created, columns added, and any warnings.
Each change is checked, recorded, and applied exactly once, which is what makes it safe on a live app. Adding is the safe move. Renaming or removing a column your pages use breaks those pages until the next build, so while people are using your app, add a new column instead of renaming an old one. A rename or removal can also stop an earlier version of your app from working if you restore it, and the panel warns you before you apply. Insight's own builds only ever add, which is why Restore can always bring back an earlier version.
Safety built in
Every project's data is kept apart from every other project's. The users table is run by DontCode and protected. Every change is checked before it runs and anything dangerous is blocked, and if a change fails partway, it is undone completely, so your data is never left half-changed.
Check your understanding
1.On the Structure map, what does a line between the orders and customers boxes mean?
2.Your live app has a page that lists orders by a column named total. What is the safest way to start tracking tax too?
3.You changed three cells in the Data view. When you press Apply, one of the values is not allowed. What happens?
Your task
Insight ProjectOpen Database and ask Insight to change how your data is organized, for example a new table or a new column on an existing one. The check passes once the change is applied.