Record page

The record page is what opens when someone clicks a row in a table, a card on a board, an event in a calendar, or a pin on a map. It shows one record: its form, its history, a conversation, its files, and lists of related records such as an order's lines or a customer's jobs.

You design the record page on the view people open it from. Different views on the same table can show different record pages, so the dispatcher and the accountant each see what they need.

What a new record page contains#

Every new view starts with one tab that holds three panels:

• Entry Details: the record's fields as an editable form.
• Activity: who changed what, and when.
• Chat: comments and discussion on the record. Type @ to mention a teammate.

Comments, activity, and related lists become available once the record has been saved.

Customize the layout#

Panel layouts#

Panels you can add#

Besides panels, a tab can hold a View, an existing view you pick, or a New view you create just for this tab. It can also hold a dashboard. A view created inside a tab belongs to that tab and doesn't appear in the sidebar.

Set up the form#

Open a panel in Customize layout to change it:

• Form Configuration sets the Field Order and, under Field Visibility & Editability, marks fields as Hidden or Read-only on this form.
• Visibility Rules show or hide the whole panel based on the record's values, for example only showing a "Delivery" panel when the status is "Shipped". Each rule compares a field with Equals, Not Equals, In, Exists, or Not Exists.

You can also click Edit form on the form itself to hide, show, and reorder fields in place, then click Done.

Hiding a field on the form only changes the form. To stop a group from seeing or editing a column at all, use an access filter.

Show related records#

A view inside a tab shows records from another table, such as the lines of an order or the jobs of a customer. To show only the records that belong to the record you have open, the related view needs an entry filter that pairs a column on the related view with a field on the open record, for example "Job lines where Job is this job".

You can ask the AI Assistant to add a related list with that filter for you.

Header buttons#

The record page header can hold buttons that start a workflow for this record, or open a link.

A workflow button passes the open record to the workflow as an input. When you create a new workflow from here, that input is already set up. An existing workflow only appears in the list if it is enabled and accepts a record as an input.

A link button can include the record's ID in the address. Write {{_id}} where the ID should go, for example https://example.com/orders/{{_id}}.

Use the arrows to reorder buttons, and the trash icon to remove one.

Inherited layouts#

A view built on an access filter inherits the access filter's tabs and buttons. When you edit an inherited tab, choose whether the change applies to This view only or to All views that inherit it. A view that only hides or renames inherited tabs keeps receiving later changes to the others. To go back to the inherited layout, click Reset to inherited.

Show a single record as its own view#

The Entry View type shows one record on its own, with the same tabs and panels, instead of a list. Use it for a screen that always shows one specific record, such as a company settings record. The record shown is the first one that matches the view's filter.

Plan a good record page#

For each record people open, decide which tabs it needs. For the form, decide which fields are read-only or only relevant in some states. For each related list, name the view and how it ties to this record. For each header button, name the workflow it starts.