Saved filters

A saved filter is a named query over your workspace's recordings, created on the dashboard's Workflow map.

You create saved filters on the dashboard's Workflow map page, so they are a Team and Enterprise feature (the Individual plan has no dashboard). A saved filter stores two things: the devices it covers and a query over their recordings.

Building the query

On the Workflow map, pick one or more devices in the Filters sidebar, then build the query with Add filter group and Add filter. Conditions inside a group are joined with And, so a recording must match all of them. Groups are joined with Or, so a recording matches the filter when it matches any group. Nothing renders until you press Apply filters.

FieldWhat it checks
StatusQuestion status: Answered, Partly answered, Not answered or No questions
AppThe apps seen in the recordings
Step typeThe kind of step, such as Click, Typed or Paste
TextApp names and step text
CreatedWhen the recording was made

Status, App and Step type take the operators is, is not, is only, is empty and is not empty. Text takes contains and does not contain. Created takes is between, is after, is before and in the last (a number of days).

Saving and updating

Choose Save and name the filter (for example Unanswered recordings in Figma). Load it later from the sidebar's filter picker; if you change a loaded filter, the button becomes Update. Deleting a saved filter is permanent.

How libraries use saved filters

Saved filters exist so that document libraries can use them as sources: every dashboard library takes at least one saved filter, and only recordings matching those filters feed the library. A saved filter means the same set of recordings wherever it is used.

Sources on the desktop app

The desktop app has no saved filters. Its libraries choose recordings with Sources, an inline query built on the create library screen.