Filtering & saved views

Most CRM list pages—Accounts, Contacts, Prospects, Tasks, and similar—share the same pattern: a filter sidebar, optional saved filters (saved views), and column sort that works independently from filters. Once you learn it on one module, you reuse the same muscle memory everywhere.

(Video — add later: Open Filter → add two conditions → Apply → Save filter → reload the saved view from the menu.)

Build a filter#

1. Open the filter panel (Filter button, funnel icon, or Filters in the toolbar—wording varies).

2. Add condition — pick a field (for example Owner, State, Created date).

3. Pick an operator — equals, contains, greater than, is empty, etc. (options depend on field type).

4. Enter a value (or pick from a list when the UI offers one).

5. Apply — the table refreshes to matching rows only.

Add multiple conditions when you need AND logic (all must match). If your org supports OR groups, the UI will show how to nest them—ask an admin if you need complex logic.

(Screenshot — add later: Sidebar with two conditions and Apply / Clear.)

Save a view (saved filter)#

After you have a useful combination:

1. Click Save filter, Save view, or similar.

2. Give it a clear name (e.g. “My accounts — West — active”).

3. Load it later from the saved filters list; rename or delete when it is obsolete.

Team tip: Agree on a naming convention so everyone recognizes territory vs campaign vs personal slices.

Combine with column sort#

Sort order is separate from filters:

• Filters decide which rows appear.

• Column headers decide in what order they appear.

Example: filter to “Owner = me”, then sort by “Last activity” descending for a call block.

Where this applies#

Use saved views on any list that exposes the same sidebar, including:

• Accounts

• Contacts

• Prospects

• Tasks

• Pipeline / Opportunities (when the list uses the same filter pattern)

If results look wrong#

• Clear filters and re-apply one condition at a time.

• Check for a hidden saved view still active.

• Ask an admin whether RLS or visibility rules limit rows even when filters are broad.