Skip to content

Filters

Not all data filtering needs a formal access policy. Sometimes you want to remove archived records from a dataset, or let dashboard viewers focus on a specific quarter. Querri has two types of filters for this — table filters and dashboard filters — each serving a different purpose.

LevelWho configures itWho sees itPurpose
Table filtersSource owners / editorsApplied to everyoneData hygiene — remove irrelevant rows globally
Dashboard filtersDashboard ownersDashboard viewersInteractive controls — let viewers slice and focus data

Table filters are static filters set by the source owner or editors. They affect everyone who views the source — unlike access policies, which vary per user. Think of them as data hygiene: removing irrelevant rows before anyone works with the data.

  • Remove test or archived records from a production dataset
  • Filter out rows before a certain date
  • Exclude internal data that shouldn’t appear in analysis
  1. Open a source’s settings (requires owner or editor access)
  2. Go to the Table Filters section
  3. Click Add Filter
  4. Select the column, operator, and value(s)
  5. Save

Supported operators include equals, not equals, greater/less than, contains, is null, between, and in/not in.

Dashboard filters are interactive controls that let viewers slice the data shown in all widgets. Dashboard owners configure which filters are available; viewers choose their selections.

TypeWhat viewers seeExample
Multi-selectCheckbox dropdownRegion: Southeast, Northeast
Single-selectRadio button dropdownFiscal Year: 2025
Date rangeDate picker pairJanuary 1 – June 30
Text searchText inputCustomer name contains “smith”
  1. Open the dashboard in edit mode
  2. Click Add Filter
  3. Choose the column, label, and filter type
  4. Optionally limit the filter to specific data sources
  5. Save the dashboard

When a dashboard has filters, a filter bar appears above the widgets. Select values and all widgets update to reflect your selections. Your filter selections are saved for your session.

Both filter types stack together with access policies in this order:

  1. Table filters — static, source-owner-defined, applied first
  2. Access policies — per-user row-level security
  3. Dashboard filters — viewer-selected interactive filters

Every layer combines with AND. A row must pass all active filters to appear. Filters can never expand access beyond what access policies allow — they can only narrow it further.

Table FiltersAccess Policies
Who sees the filter?EveryoneOnly the assigned user
PurposeRemove irrelevant rowsRestrict data per user
Who can manage?Source owners and editorsAdmins only