See your records as a table or a kanban

A list of records has no single right way to show itself. The same set of contacts reads as a table when you are checking phone numbers, and as a kanban when you are following progress.

In Standards, those two readings are two layouts of the same list. Not two copies.

The tabs of a list

A list carries tabs. Each one has its own columns, its filters, its sort and its layout.

A telling example: on your contacts, an “All” tab as a table with the name, the email and the status; an “Active” tab with the same table narrowed to active contacts; a “Pipeline” tab as a kanban, grouped by stage.

Three readings, one set of data. Editing a record in one updates it everywhere.

Table

The default layout. One row per record, one column per field.

You choose which columns show and how wide they are. You sort. You filter on any field, combining several conditions.

Kanban

Columns, and cards that move from one to the next.

Kanban needs a field to build its columns: a status, a stage, a priority.

A card can show an owner at the bottom left and a date at the bottom right, which is usually enough to decide without opening the record.

Creating a record

The add button of a list behaves in three ways, depending on what the view asks for.

• Open the record: the record is created and you are taken to it. Best when there is a lot to type.
• Add a row: an empty row appears in the table and you fill it in place. The fastest for short entries.
• Open a window: a panel opens on top, you type, you close it.

A view can be read only

Some lists are deliberately frozen: no editing in the cells, no creating, no deleting. That is a configuration choice, not a permission you are missing. If you need to write there, it is the view that has to change, not your role.