> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clustr-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Saved Views

> A view is the question you keep asking

A view is a saved filter over your Accounts, People, or Connectors table: which
rows, in what order, with which columns. Save one and it sits in the sidebar
next to the table it filters, ready the next time you open Clustr.

A view is not a snapshot. It answers its question live, every time you open
it, against whatever is true right now. "A-grade, Burning, not in HubSpot" is
a view. So is "Deal in Negotiation or Proposal, path at 80% or better." Anything
you can filter the table on, you can save.

## Creating a view

Filter a table the way you want it, then **Save view**. Give it a name. Two
switches decide who else sees it:

* **Shared** makes the view visible to your whole workspace. Anyone can open
  and read it; only you can rename, refilter, or delete it unless you clear
  this and someone else re-saves it.
* **Pinned** puts the view in the sidebar's navigation tree, so it's one click
  away instead of a search.

## Alert and Automate

Every view carries two buttons, right next to Save view:

* **Alert** sends a notification the moment a record enters the view: a Slack
  channel, a DM to the record's owner, or an email. One click, one picker,
  done.
* **Automate** opens the [Workflow](/workflows) editor with this view already set as
  the trigger, so you can add more than one action, watch records leaving the
  view too, or run on a schedule instead.

Alert is the fast path to the single most common ask: "tell me when." Automate
is the same object with more room — see [Workflows](/workflows) for what a Workflow can
do once you're there.

## What drives a Workflow

A view's filters are compiled into the exact query your table runs. That
same query is what a Workflow uses to decide who's a member, so a Workflow never sees
a different set of records than the table you built it from. A view saved
before this existed needs one re-save before it can drive a Workflow; the Workflow
editor tells you when that's the case.

## Reading a view's members

Every saved view exposes its current member list: who's in it right now, with
the handful of facts (grade, temperature, tier, tags, owner, deal stage,
best path) that describe why they're there. This is what a Workflow reads, and
it's also available directly if you want to build your own automation against
it — see [List saved view members](/api-reference/get-saved-view-members).