Saved Filter Sets / Named Views for Dashboards

[metalshanked]

When using complex dashboards with many filters, end-users (e.g., business stakeholders) often need to apply the same combination of filters repeatedly to get to their specific, relevant view of the data.

For example, a regional manager might always apply the same three filters every morning:

• Region = 'North America'
• Time Range = 'Last 7 days'
• Product Line = 'Enterprise Hardware'

Currently, the user must manually set these filters every time they visit the dashboard. The only alternative is to bookmark the very long, state-encoded URL, which is not user-friendly, is hard to share, and can break if the dashboard structure changes. This repetitive process is tedious, error-prone, and a significant friction point for non-technical users.

I propose the ability for users to save and name a combination of applied filters as a "Saved View" directly on the dashboard.

The workflow would look like this:

1. A user navigates to a dashboard and applies their desired filters.
2. A new "Save View" button would be visible near the filter bar.
3. Clicking it opens a small dialog where the user can give their filter set a name (e.g., "My Weekly NA Report").
4. The dashboard would then have a new dropdown menu, perhaps labeled "Views," containing "Default View" and any saved views like "My Weekly NA Report."
5. Selecting a saved view from this dropdown would instantly apply the corresponding set of filters to the dashboard.

Enhancements could include:

• Permissions: Ability to save views for "Only Me" (personal) or "All Users" (shared, for dashboard owners).
• Direct Linking: Each saved view should have a clean, shareable permalink.
• Management: A simple interface to rename or delete saved views.

The current alternatives are:

• Manually re-applying filters: This is the core problem—it's inefficient and annoying.
• Bookmarking stateful URLs: These URLs are long, ugly, and fragile. They are not a scalable or user-friendly solution for sharing common perspectives on data.

[marek-nowak]

Fully agree.
We need such feature as well. Great description.

[RahulBisht001]

@marek-nowak In my current organisation, we are using Superset and are encountering this same issue that requires resolution. Given that we are leveraging open-source technology, I would like to contribute to developing this feature as a way to give back to the community.

[markoburcul]

Definitely a killer feature request. We have some complex dashboards in our organization that have many filters and this would be a time saver.

[LiamTorrelli]

Superset actually shipped this once. "Filter Sets", behind DASHBOARD_NATIVE_FILTERS_SET, around 2021. Name a combo, pick it from a dropdown — basically the workflow you're sketching with "My Weekly NA Report".

4.0 deleted the whole thing in PR #26369. Honest maintenance call on their side — UI bugs, hydration races, broke whenever someone edited the dashboard. But the friction you're describing didn't go away. Permalinks are anonymous one-offs. native_filters_key URLs expire from server cache. Duplicating the dashboard copies structural drift forever.

The part that killed the original (and why a naive re-add would fail again): what happens to a saved view when someone renames Product Line or adds a filter? Old code crashed on that. We rebuilt named presets in our fork with drift detection on every render (warning triangle + block if applying would produce bad SQL), one-click SYNCHRONIZE when the dashboard structure shifts, per-user default presets on open, and shared team presets with ownership scopes.

I wrote the removal history, the workaround gaps, and the architecture: https://drafted.work/blog/superset-filter-presets