Views

Back to the guide

A view decides how records are shown: which columns, in what order, grouped how, and as a table or a kanban board. It never changes what is stored.

Views sit in a bar above the table. Switching between them changes only what you are looking at.

Table or kanban

Table is the default. Columns you choose, one page at a time.

Kanban groups records into columns by a status field — Opportunities by Stage, for instance — and you drag cards between them if your role allows it. Dragging a card changes that record's status, and the change is recorded on its timeline.

A kanban on an object shows the records on the current page rather than all of them. A kanban on a list shows every entry.

Creating and changing

If your role allows writing, you can create a view, rename it, delete it, set which one opens by default, and choose what it groups by.

A useful habit is one view per way of working rather than one view you keep reconfiguring: a wide table for data cleanup, a narrow one for scanning, a kanban for the pipeline meeting.

Columns

Columns can be resized by dragging, and widths are remembered.

If you have permission to change the schema, you can add a new attribute directly from the table rather than going into object settings first. That adds a real field to the object, not just a column in the view.

Filtering

Filtering happens in the database, not in your browser. Filtering a large object applies to every record, not only the page in front of you.

Changing the filter or typing in search returns you to page 1.

What you cannot do yet

Sort every record by clicking a column header. Sorting applies to the current page; records are paged newest first.
Add a "next task due" or "last activity" column.
Share one person's view configuration as a template.