Chapter 3/8 • 15 min read

Lists & Views

Turn raw CRM data into focused views your team uses every day.

⏱️ En bref : Lists and Views are how you turn Attio's data into actionable workflows. Lists are saved filtered subsets of records (e.g., 'Top 50 prospects'). Views are visualization modes for any list (Table, Board, Calendar). Build the right Lists for each role, and your team stops asking 'where do I find X?'.

Lists vs Views: the distinction

Two concepts often confused:

  • List: a saved subset of records, defined by filters or manual selection. Example: "Enterprise leads" filters People where company.headcount > 500 AND status = "Lead"
  • View: a way to display a List or any record collection. Table, Board, Calendar, Timeline. Same List can have multiple Views

Think Notion: Lists = databases, Views = views on those databases.

Creating a List

From any object collection (e.g., All People), click "+ List" in the sidebar. Two creation modes:

  • Filtered list: define criteria (e.g., source = Inbound AND created_at > 30 days ago). The list updates automatically as records change
  • Manual list: handpick records (e.g., your top 50 ABM accounts for Q2). Static unless you edit it

Filtered lists are dynamic, perfect for "what should I work on today" type queries. Manual lists are static, perfect for campaigns and curated cohorts.

Filter logic

Attio's filter UI supports:

  • AND/OR combinations with grouping (parentheses)
  • Operators per type: contains, equals, greater than, before, after, is empty, is not empty
  • Date ranges: relative (last 7 days, this quarter) or absolute
  • Reference filters: filter People where their Company has industry = "SaaS"

The reference filter is powerful and often forgotten. It lets you query People by attributes of their Company, or Deals by attributes of their Owner, etc.

💡 Save the queries you run twice

If you find yourself filtering manually for the same criteria more than once, save it as a List. The 30 seconds saved per use compounds quickly across the team.

The 4 view types

  • Table: spreadsheet-style, the default. Best for browsing many records, sorting, bulk editing
  • Board (Kanban): cards grouped by a Status field. Best for pipelines (deals, lead status, project phases)
  • Calendar: records placed on dates. Best for time-based data (meetings, renewals, follow-ups)
  • Timeline: similar to calendar but shows duration. Best for projects and contracts

Switch view by clicking the toggle in the top-right of any list.

Grouping in Table view

Tables can be grouped by any attribute. Common groupings:

  • Group People by Owner → see workload distribution
  • Group Companies by Industry → spot concentration
  • Group Deals by Stage → quick pipeline visualization without leaving table
  • Group Subscriptions by Renewal month → spot churn risk windows

Grouping is set per view, so you can have one Table grouped by Owner and another grouped by Status on the same List.

Common Lists I deploy for B2B clients

  • "Today's hot leads": People with last_activity in last 24h, status = Qualified
  • "Stalled deals": Deals with no activity > 14 days AND stage not in (Won, Lost)
  • "Owners overload": Owner grouping showing # active deals per rep
  • "Q2 enterprise pipeline": Deals where Company.headcount > 500 AND expected_close in Q2
  • "Renewal risk": Subscriptions with renewal_date in next 60 days AND health_score < 7
  • "ABM target accounts": manual list of top 50 strategic prospects

Sharing Lists across the team

Lists can be:

  • Personal: only visible to creator
  • Workspace: visible to all team members
  • Shared with specific users: visibility scoped

For role-based dashboards, create workspace Lists per role (Sales, RevOps, CS) and pin them in the sidebar. New team members get instant orientation.

📘 Lists also drive workflows

Workflows can trigger when a record enters or leaves a List. So a List can act as a "tag" that triggers automation. Example: when a Person enters the "Activated" list, trigger an email sequence. See Workflows chapter.

For automating actions based on List membership, see Workflows. For the underlying structure, see Data Model.