Table
Table pages present records from a table using one or more visualizations: Grid, Gallery, Kanban, List, Calendar, or Timeline.
A Table page connects to a table and presents its records through one or more visualizations. Add several visualizations to give users different perspectives on the same data; when a page has more than one, a switcher lets users flip between them.
Common settings
These settings are available for every visualization on the page:
| Setting | Description |
|---|---|
| Filters | Limit which records the visualization shows. Visualization filters combine with page-level filters. |
| Sorts | Define the record order. |
| Visible fields | Choose which fields are shown, and in what order. |
| Colour records by | Colour records based on a field's value. |
| Click into details | Open a record detail page when a user clicks a record, as a modal or side sheet. |
| Inline editing | Allow users to edit field values directly in the visualization. |
| Add / delete records | Allow users to create and delete records from the page. |
| Add record through form | Route the page's add-record button through a reusable form page instead of an inline row. Turning it on binds the button to the first available form for the table, which you can then change. If the table has no form page, the button stays unbound until you pick one. |
Visualizations
Each visualization has its own settings, edited from the properties panel in the builder.
Grid
Work with data in a spreadsheet-style table. Grid suits data-heavy workflows where users need to scan many fields at once: operations trackers, content pipelines, or any page that doubles as a lightweight data-entry surface.
Adjust the reading density with Row height (Small, Medium, Large, or Extra large), and turn on Show field descriptions to surface each field's description in its column header.
Group by stacks records under collapsible headers. Add up to three levels with New Subgroup, drag to reorder them, and set a direction per level: ascending or descending by value, or by record count (Count (9 → 1) and Count (1 → 9), available on Grid only). Turn on Hide empty groups to drop the uncategorized group.
Summaries let you pick an aggregation per column, shown in the grid footer and in each group header. Picks are saved with the visualization, so they survive a reload and carry through to the published interface.
Gallery
Records as visual cards, led by an image. Gallery works best when the picture is the point: portfolios, product catalogues, asset libraries, or property listings.
The card cover comes from an Image field, shaped by an aspect ratio and a fit image control that decides whether the photo fills or fits the frame. Pick a Theme (Card or Poster) and a Style (Rich or Compact) to set the overall look, then choose the Title field and its size for the caption under each cover.
Cards per row is Auto by default, which adapts to the available width, or a fixed 1 to 6 for a strict grid. To keep cards clean, decide whether to display field names alongside values and whether to hide empty fields on cards so blanks never leave gaps.
Kanban
Records as cards stacked into columns, one column per value of a single-select field. Kanban is the natural fit for anything that moves through stages: request triage, content production, hiring, or a sales pipeline.
Stacked by (required) picks the single-select field that defines the stacks; each option becomes a column, with an Uncategorized stack for records that have no value. Where the visualization allows inline editing, dragging a card to another stack updates that field. Stacks can also be collapsed to slim pills to keep wide boards manageable.
For appearance, choose a Theme (Board, Columns, Tint, or Compact), and give cards a cover through an Image field with a fit image control. Hide empty stacks removes columns that hold no records, and display field names controls whether cards label their values.
List
Records as a compact list, optionally nested into a multi-level outline through Levels. List shines when records only make sense in context of their parent: deliverables under campaigns under brands, tasks under projects, or line items under orders. A footer shows the total record count.
A Prefix field renders ahead of each row's title, and row height and wrap headers control density, with headers wrapping instead of truncating. For organisation, Group by collects records under collapsible headers, show field descriptions surfaces field descriptions in column headers, and collapse all by default starts every section collapsed so expanding is the viewer's action.
Levels
Levels nest records beneath their parent records using link fields, turning the list into an outline. Levels are configured from the innermost record outwards: the first level is the page's source table, and each level you add above it is a parent table reached through a link field.
Each level is configured independently: which fields it shows, its sort order, and filters for which records it includes. A label captions the level's sections, defaulting to the link field's title, and click into record details gives the level its own record detail page target, so clicking a campaign and clicking a deliverable can open different detail pages.
Levels belong to the List visualization, but when a page has one, they are also reachable from Levels in the page's Data section.
Working with records
Where the visualization's editing options allow it, users can edit cells inline and type directly into a cell to start editing. + New record appends a row inline, either at the end of a flat list or inside the innermost section of a leveled list, where the new record is linked to its parent automatically. Adding at a parent level, or with inline adding turned off, opens the page's create form instead.
Calendar
Records plotted on a calendar using date fields. Use it for anything date-anchored that people plan around: content calendars, editorial schedules, bookings, or delivery dates.
Date range picks the start (and optionally end) date fields; with an end date, multi-day records span across days. Each event is labelled by the Label fields you choose, with per-field bold, italic, and underline formatting, plus an optional label image field for a thumbnail on the event.
The Event display theme (Bordered, Dot, Solid, Minimal, or Pill) sets how events render on the month grid, and the Initial view decides what viewers land on: the default position, timescale, date row height, and whether weekends are shown.
Timeline
Records as horizontal bars along a time axis, so overlaps, gaps, and durations are visible at a glance. Timeline suits schedules where the span matters as much as the date: production phases, campaign plans, resource allocation, or roadmaps.
Date range sets the start and end date fields that give each bar its span. Bars carry the Label fields you pick, with a wrap labels option, while row height and Record width (fill the timescale, or a fixed width) tune the layout. Group by splits bars into swimlanes, for example one lane per phase or per assignee, and the Initial view fixes the starting timescale anywhere from day up to year.
Show dependencies draws dependency arrows between linked records, turning the timeline into a Gantt-style chart. The arrows follow the table's date dependency rule, which links each record to its successors through a link field, so finish-to-start chains read as a waterfall.
Peek cards
On Calendar and Timeline, clicking a record opens a peek card with its details. The card appears whether or not Click into details is enabled; when it is disabled, the card simply omits the expand affordance. If the visualization allows adding and deleting records inline, the card also offers Duplicate and Delete.
Switching visualizations
Users switch between the page's visualizations with the switcher shown at the top of the page. You can also let a tab filter activate a specific visualization per tab, for example a "Board" tab showing Kanban and a "Schedule" tab showing Timeline.