Views
Saved combinations of filters, sorts and grouping over a data object.
A single data object can serve many purposes, and different people need to see it differently. A view is a saved lens over an object: a particular combination of filters, sorting, and grouping that you can name and return to.
What a view captures
A view doesn't change the underlying data; it changes how you look at it. It remembers:
- Columns: which fields it shows, and in what order.
- Filters: which records to show (for example, only open positions, or only this quarter).
- Sorting: the order they appear in.
- Grouping: how they're clustered, if at all.
Switch to a different view and the same object reframes instantly, without touching a single record.
Why views exist
Two things make views valuable. First, focus: instead of scrolling a full object, each person opens straight to the slice that matters to them. Second, consistency: when a view is saved and shared, everyone looks at the data the same way, so a team's numbers line up rather than drifting apart because two people filtered differently.
Views are how a broad, shared dataset stays useful to narrow, specific jobs.
Looking is not changing
Because a view is a way of reading, shaping one is never a risk. Changing filters, sorting or columns cannot alter a record, and on a record grid the data itself is read-only until you deliberately turn on edit mode. See Reading and editing.
Where views show up
Views live on the data object itself, and the same saved lens can feed other surfaces. A canvas widget, for instance, can read from a view so a chart always reflects the intended slice of data. That connection is what keeps a dashboard honest as the underlying records change.
Tasks and Files carry views too, as a strip of tabs across the top of their list, each with its own columns, filters and sort. The mechanism is the same one, applied to the records those pages hold.
One object, and its neighbours
A view is still a view of exactly one data object. What it can now do is borrow columns from another one, so a question spanning two objects is answered in the view rather than in an export. Your row count does not change and the borrowed columns are read-only, which keeps a view a lens rather than a second copy of the data. See Merge with other data.
The Manage data views page in the Data section covers how to build and save views. For the tab strip on Tasks and Files, see Task views and Organize files.