Schema map & relationships

The schema map is a live diagram of every table in a workspace and the arrows connecting them, and it lets you create new relationships by dragging between tables. For ad-hoc, one-off links between two specific records, open a record's detail page and use Add a one-off link. Read the schema map Open Schema & relations from Manage workspace at the foot of the rail. Every table you can see is a card with its record count, and every Relation field is a line between two cards, labelled with the field the link travels. The map is ranked, so what a record belongs to sits above it: customers above their orders, orders above their lines. The key under the map shows how to read a line: many, one, belongs inside (the records live inside their parent and go with it), and dashed for a relation nobody has linked through yet. Click a table to focus it. Everything it doesn’t connect to fades, and the panel beside the map shows its record and field counts, what it points at, what points at it and anything nested inside it, with Open records and, if you can change the schema, Edit fields. Click a line to read the relationship as two sentences, one for each direction, with how many links it carries right now. The toolbar totals the tables, relations and links. Some of its counts are lenses: click standalone to see only the tables that link to nothing, or not linked yet to see only the relations nobody has used. Neither is a warning. A standalone table is often reference data, and every new relation starts out unused. To connect two specific records that no relation field covers, open either record’s detail page and use Add a one-off link. Move around the map Scroll to pan, or drag an empty part of the canvas. Ctrl+scroll zooms in on the pointer, the − and + buttons zoom too, and Fit brings the whole map back on screen. Type in Find a table… (or press /) to highlight the tables that match; when only one does, the map moves to it. Drag a table to rearrange the map. An Admin’s or Editor’s arrangement is saved for everyone in the workspace; anyone else can still move tables around, but those moves aren’t saved, and the key under the map says so. Auto-layout lays every table out again by what it belongs to, and asks first if there is an arrangement to lose. Folders on the map Once your tables sit in two or more folders, the map draws each folder as a labelled region with its tables inside, and the top-level tables come first, as they do in the rail. Each folder is laid out on its own, so an area of the business reads as one block rather than being scattered across the page. A line that crosses from one folder into another is drawn a little heavier. Those are the places where one area hands work to another, such as an order in Sales becoming a work order in Production, and the across folders lens in the toolbar shows only those. Click a folder’s name to see its tables and every link into and out of it. Drag the name to move the whole folder at once. A region is drawn around wherever its tables are, so dragging one table outwards takes the folder’s edge with it. A private folder is drawn only for people who can see inside it; anyone else sees neither the folder nor its tables. To move a table into a different folder, use the rail: right-click the table, or drag it onto the folder’s heading. Draw a relationship by dragging If you can change the schema, every table card has a small round + port on the right edge of its header. Press it and drag: a line follows your cursor, and the table you hover over highlights. Drop it there. A dialog titled with the two tables appears, Clients → Projects for example. The column name is filled in with the target table’s name; change it if you like. Under What kind of link?, pick one of the options. Each is described in a sentence, and the box below spells out the link in both directions and what happens when a record is deleted. Then press Add the column. This adds a Relation field to the table you dragged from, pointing at the table you dropped on. Nothing is linked yet, so your existing data, views and reports don’t change until you fill the field in on some records. Press Cancel or Esc to back out. Link two specific records Most connections are best expressed as Relation fields — defined once on a table and filled in per record. For a genuine one-off between two exact records that no relation field covers, open a record's detail page and use Add a one-off link. Pick a Target record, give the link a Key (its connection name) and an optional Label, then press Add link. The new link appears under Manual links on that record, and the record it points at lists it under Records that use this — click either side to open the other. Name the connection The link's Key is its connection name — the label RowFold groups links by. The optional Label is a human-friendly note shown alongside the connection. • A Key that matches a Relation field on the starting record's table is rejected — you'll be told to set that field on the record instead, which keeps the one-off link from being wiped the next time the record saves. • Creating an identical link twice (same two records, same Key) quietly does nothing; no duplicate is stored. See a record's links A record's own detail page is where its links live: Manual links lists the one-off links you added from it, each with an × to remove it, and Records that use this gathers every record that links to this one — through a Relation field or a one-off link — grouped by table with counts. Click any chip on either side to open that record. Choose links or Relation fields Every link is a one-way arrow: it runs from a starting record to a linked record and carries a name. A record can sit on either end of any number of links, so one-to-many and many-to-many shapes both work. Relation fields are the durable version: defined once on a table, filled in per record, and RowFold keeps the map's arrows in sync with their values. Lookup and Rollup fields — which pull or aggregate values across a relation — are added in a table's field editor, not on the schema map; the map just lists them on the table's card like any other field. Preview multi-level records (concept) The page at /MultiLevel is an interactive design concept for nested, multi-level records — a relation marked as owning its children so linked tables nest inside their parent. It is visible only to super admins (an app-operator allowlist), has no link in the rail, and everything on it is hard-coded sample data: edits are never saved, and the Submit → button on the form surface sends nothing. Four numbered tabs show the same idea from different angles: Schema · composition (a field inspector with ownership modes Reference, Owns children, and Belongs to parent), Record panel · document (parent fields with owned children and grandchildren embedded inline, plus live rollup totals), Public form (LiveForm) (the same nesting as a fillable form with cross-level validation), and Ledger view (one row per parent, expandable to depth L0, L1, or L2). A dropdown pill in the top bar switches between two demo datasets — Orders → Line items → Serials and Inspections → Rooms → Defects — and switching resets any edits. A floating Tweaks panel toggles Comfortable/Compact density and whether hidden conditional sections show as ghosted hints. Tips • Click a table to focus it, then use Open records in the panel beside the map to go to its grid. • The ×N on each arrow is a live count of actual record-to-record links of that type. • To link two specific records that no relation field covers, open either record's detail page and use Add a one-off link. • Use Fit to bring the whole map back on screen after zooming in. • Remove a one-off link with the × beside it under Manual links on the record's detail page. • In a workspace with folders, the across folders lens shows only the links from one area of the business to another. Good to know • A relation nobody has linked through yet is drawn as a dashed line, and the not linked yet lens finds them all. That means it is new, not broken. • The map shows one workspace at a time; if you belong to several, make sure you arrived from the right one. • To start a relationship, drag from the small + port on a card's header. Dragging anywhere else on the card moves the table, and clicking it focuses the table rather than opening it. • A connection name that matches a Relation field on the starting record's table is refused; set that field on the record itself rather than adding a one-off link. • Creating the same link twice shows no error but stores nothing new. • Everything on the multi-level concept page is sample data — edits are never saved and reset when you switch the demo dataset. Who can do what • You must be signed in to open the Schema map. • The schema map and the one-off link picker show only workspaces you are a member of — never other tenants' data. • A link is created only when both records live in workspaces you belong to; the server rejects anything else. • Dragging a new relation on the schema map is accepted by the server only for tables in workspaces you belong to. • The multi-level concept page is restricted to super admins via an app-operator allowlist — workspace Admin is not enough.