Freezing the Page Filter Section During Scroll in Databricks

[Seunghyun]

I have a question regarding Databricks Dashboards.

I would like to fix the filter area within the dashboard so that it remains visible at all times, even when scrolling up or down. Is there a way to make the Page Filter area 'sticky' or frozen, excluding the Global Filters

[Ashwin_DSA · Accepted solution]

Hi @Seunghyun,

Right now, there isn’t a way to make the page-level filter bar itself “sticky”, so it stays visible while you scroll. The only sticky behaviour that exists today is for things like pivot table headers, not for dashboard filters.

The closest built-in workaround is to use Global Filters:

• Open the Global Filters panel from the filter icon in the dashboard.
• Move your key filters into that panel.
• If you publish the dashboard with the global filter panel open, it will open by default for viewers and stay visible while they scroll through the page.

Docs for reference: search for “Use dashboard filters” in the Databricks documentation, which covers global filters and page-level filters in more detail.

Pinned/sticky page filters are a known feature request, but they’re not available yet. If this is important for your use case, I’d recommend filing or upvoting an idea via your Databricks account team so PM can track demand.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

Regards,

[SteveOstrowski]

Hi @Seunghyun,

AI/BI Dashboards do not currently have a built-in option to make page-level filters sticky or frozen during scroll. However, there are a couple of approaches you can use to keep filters accessible for your viewers.

OPTION 1: USE GLOBAL FILTERS (RECOMMENDED)

Global filters live in a dedicated side panel that stays visible as users scroll through the dashboard content. Here is how to set this up:

1. In the dashboard editor, click the filter icon in the upper-left corner to open the Global Filters panel.
2. If you already have page-level filter widgets on your canvas, you can move them to the global panel: right-click the filter widget, select Cut (or Ctrl+X / Cmd+X), then right-click in the Global Filters panel area and select Paste (or Ctrl+V / Cmd+V).
3. When you publish the dashboard with the Global Filters panel open, it will remain open by default when viewers load the published dashboard. This means your filters are always visible, regardless of scroll position.

Global filters apply across all pages in your dashboard, so this works especially well if you have filters that should be consistent across pages.

OPTION 2: POSITION FILTERS AT THE TOP OF THE CANVAS

If you need to keep your filters as page-level widgets (applying to one page only), consider placing them at the very top of the dashboard canvas. While they will not be sticky, they will be the first thing viewers see. Keeping the dashboard compact or using tabs/multiple pages can reduce the amount of scrolling needed.

ACTIVE FILTERS BAR

One additional feature to be aware of: any filter (global or page-level) that is not set to its default "All" value automatically appears in the active filters bar near the top of the dashboard. This gives viewers a quick summary of which filters are currently applied, even if the filter widget itself has scrolled out of view.

For more details, search for "Use dashboard filters" in the Databricks documentation, which covers how to create and manage global filters, page-level filters, and the active filters bar:
https://docs.databricks.com/en/dashboards/manage/filters.html

If sticky page-level filters are important for your workflow, I would encourage you to submit a feature request through your Databricks account team or via the Databricks Ideas portal so the product team can track demand.

* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.

If this answer resolves your question, could you mark it as "Accept as Solution"? That helps other users quickly find the correct fix.