Lists and views

Lists and views help teams work with focused slices of data. They should support a workflow without replacing the underlying object model.

Object views

Object views are saved ways to look at records from one object. Use them when the team needs different columns, filters, sorting, or view types for the same source of truth.

Lists

Lists group entries around a workflow. A list can have its own attributes and views while still being connected to a parent object.

Use lists for focused work such as target accounts, event follow-up, renewal candidates, enrichment review, or campaign preparation.

Boards

Boards are for task workflows. Use a board when the primary question is “what work needs to move through stages?” Use a list when the primary question is “which records belong to this focused set?”

Choosing the right structure

Need	Use
Durable customer or company data	Object
One entry in that data model	Record
Saved table or kanban perspective	View
Focused group of records or entries	List
Stage-based work execution	Board

Setup flow

1. Start from the object

   Confirm the source object before creating a list.

2. Create the list

   Name the list around the workflow, not the department.

3. Add list-specific fields

   Add fields that only matter inside this workflow.

4. Create views

   Add saved views only when users need a different way to work with the same list.

Related guides