Skip to content

How Filter Presets Work

Filter presets are shared across the workspace. Visibility depends on your team's datastore access; editing, renaming, and deleting depend on your workspace role and whether you created the preset. This page explains those behaviors in detail.

What a Preset Contains

Item Description
Name The name shown in the Saved Filters dropdown. Unique across the workspace; up to 255 characters.
Description Optional description shown under the name.
Datastores The source datastores the preset filters by.
Tags The tags the preset filters by.
Created by The user who created the preset. Does not change after creation.
Edited by The user who last modified the preset.
Last updated When the preset was last modified.

Presets created before ownership tracking was introduced may not have a "Created by" or "Edited by" value.

Who Can See a Preset

A preset appears in your Saved Filters dropdown only if you have access to all the datastores it references:

  • Admin: Sees every preset in the workspace, regardless of which datastores it references.
  • Member and Manager: See only presets whose datastores their team can access. If even one of the preset's datastores is outside their team access, the preset is hidden.

The same rule applies whether you are listing, viewing, updating, or deleting a preset.

Who Can Edit or Delete a Preset

Editing, renaming, and deleting a preset depend on your workspace role and whether you created it:

  • Admin and Manager: Can edit, rename, or delete any preset they can see.
  • Member: Can edit, rename, or delete only the presets they created. They can still apply any preset they can see.

Presets without a recorded creator can only be modified by Admin or Manager. See Permissions for the full matrix.

How the URL Restores a Preset

When you open the Explore page, the selected preset is restored in this order:

  1. The ?filter=<id> parameter in the URL, if present and the preset is accessible to you.
  2. The preset you had selected in the current browser tab, if any.
  3. None: no preset selected, and no filters applied by default.

If the URL references a preset you cannot access (deleted, or its datastores are outside your team's access), the URL parameter is cleared and the page falls back to the default unfiltered view without showing an error.

What Happens When a Preset Becomes Unavailable

If the preset you have selected becomes unavailable, the Explore page clears the selection. This happens when:

  • Another user deletes the preset.
  • A team membership change removes your access to one of the preset's datastores.
  • A datastore referenced by the preset is deleted.

The Explore page returns to the default unfiltered view without showing an error.

Name Uniqueness

Preset names are unique across the workspace. Attempting to create or rename a preset to a name that already exists shows an error and the preset is not saved.

Names are case-sensitive, so Production and production are treated as different names. Whitespace at the start or end of a name is ignored.

Updating a Preset

When you update a preset, only the fields you change are modified. Other fields keep their current values.

To clear the datastores or tags on a preset, save it with no datastores or tags selected.

The "Edited by" and "Last updated" values refresh on every successful save, even when no actual change is made.

Loading Insights Filtered by a Preset

Applying a preset to the Insights tab uses the preset's saved datastores and tags as filters. The report date defaults to today, and the timeframe comes from the preset (or an override). Insights for a preset always show the latest data.

For programmatic access, see the API page.