Back to Blog

Power BI Filters Pane - Format Lock and Hide Filters Like You Mean It

May 18, 2026•9 min read•Michael Ridland

The Filters pane is the most overlooked part of any Power BI report. Most teams accept the default grey panel on the right and never touch it. Then they wonder why their reports feel like internal admin tools instead of products users actually want to use.

This is a fixable problem. The Filters pane has had proper formatting controls for years now, and you can lock filters, hide filters, theme the whole pane, and bookmark its open and closed state. Used well, it is the difference between a report that looks like it was built by a developer in a hurry and one that looks like a small piece of software. We treat this as a basic quality bar on every Power BI engagement, and it is one of the things our Power BI consultants check during model reviews.

Why the default Filters pane is a problem

The default Filters pane has a few issues that make reports look amateurish.

The grey background does not match your branded report. The font is generic. Applied filters look the same as available ones, so users cannot tell at a glance what is filtering the data. And worst of all, every field you drop on the canvas gets a filter card created automatically, including fields that should never be filterable by an end user. Things like internal IDs, system codes, audit timestamps, and the dozen helper columns your model needs that no business user should ever see.

If you do not curate the Filters pane, your users open the report and see twenty filter cards, most of them meaningless. They get overwhelmed, they pick the wrong one, and they email you asking what the difference is between OrderDate and OrderDateUtc. The fix is to actually design the Filters pane.

Build the pane intentionally

Start with a hard rule: only fields users should genuinely filter by belong in the Filters pane. Everything else gets hidden.

When you add a visual, Power BI automatically populates the Visual level filters section with every field used in that visual. Some of these are fine to leave. Most should be hidden. The pattern we use:

  1. Build the visual the way you want it
  2. Open the Filters pane and look at the visual level filters
  3. For each one, decide: would a business user ever want to filter this? If no, hide it.
  4. Add the genuinely useful filters at the Page or Report level so they apply across multiple visuals

A common example. You build a sales table that shows OrderId, CustomerName, OrderDate, SalesAmount, and SalesRegion. Power BI adds all five fields as visual filters. The only ones a user would reasonably filter by are OrderDate and SalesRegion. Hide OrderId, hide CustomerName (let them search the table directly), hide SalesAmount (they will use the table sort instead). Two visible filter cards, both useful.

This is the difference between a report with eight thoughtful filters and a report with forty noisy ones.

Lock filters that should not change

Lock is the underused sibling of Hide. A locked filter is visible to the user but they cannot change it.

When is this useful? Anytime you have a data scope that must apply but you want users to see it is being applied. Examples from real client work:

  • A regional manager's report locked to their region. They see "Region = Queensland" in the Filters pane but cannot change it to NSW.
  • A financial year filter locked to the current FY for a year-to-date dashboard. Users can see the YTD scope without accidentally breaking it.
  • A status filter locked to "Active" on a customer list, with a sister report that shows "Inactive". Splitting reports by lock state is sometimes cleaner than letting one report show both.

Lock is great because it makes data scope explicit instead of hidden. Hidden filters are dangerous when users are not aware they exist, because they might assume the data is unfiltered when it is not. A locked filter announces itself.

Hide filters when they are noise

Hide is the right tool for data cleanup filters and internal scope rules that users do not need to know about.

The most common use case is excluding nulls or test data. You almost always want a filter like IsTestRecord = false or LoadStatus != 'Failed' applied at the report level. The user does not need to see this, and showing it would just create questions you do not want to answer.

Another use case is row-level security helper filters. If you have a column that limits visibility based on user ID, that column needs to be filtered on but should never be edited by the end user. Hide it.

One trap to know. Hidden filters do not show up in the read-only filter list when users hover over a visual. This is intentional but it means hidden filters are genuinely invisible to your users, which makes them dangerous if used carelessly. We make a rule on client work that hidden filters get documented in the report's About page so there is a paper trail of what is being applied silently.

Format the pane to match your report

This is where most reports skip a step that takes ten minutes and changes how the whole report feels.

The Filters pane has its own formatting section in the Visualizations pane, accessed by clicking on the report canvas background and going to Format. You can set:

  • Background colour for the pane itself
  • Border colour and on/off
  • Title and header font, colour, text size
  • Background and border for filter cards in their default state
  • Background and border for filter cards in their applied state
  • Input box colour for filter inputs

The single highest-impact change you can make is giving Applied filter cards a different colour from Default ones. We usually use a brand-coloured background for Applied and a neutral grey for Default. The result is that a user can glance at the Filters pane and immediately see what is active. This sounds small. It changes the entire feel of using the report.

The second highest-impact change is matching the pane background to your report's wallpaper colour. If your report has a dark navy header, do not leave the pane white. Pick a tone that sits inside the brand palette. This makes the pane feel like part of the report rather than a panel grafted on the side.

Theme files for consistency at scale

If you are running more than a handful of reports, formatting each pane by hand is a waste of time. Power BI theme files include settings for the Filters pane and filter cards under the outspacePane and filterCard keys. Set them once in your organisation's theme and every new report inherits the styling automatically.

A minimal snippet that gets you most of the value:

"outspacePane": [{
    "backgroundColor": { "solid": { "color": "#F4F4F6" } },
    "borderColor": { "solid": { "color": "#E0E0E5" } },
    "border": true
}],
"filterCard": [
    {
        "$id": "Applied",
        "backgroundColor": { "solid": { "color": "#0078D4" } },
        "foregroundColor": { "solid": { "color": "#FFFFFF" } }
    },
    {
        "$id": "Available",
        "backgroundColor": { "solid": { "color": "#FFFFFF" } },
        "foregroundColor": { "solid": { "color": "#000000" } }
    }
]

Use your actual brand colours, obviously, but the structure above is the pattern. Applied cards in your primary brand colour, default cards in a clean neutral. We bake this into the theme on every Australian client we work with through our Microsoft Fabric consulting, and it pays for itself the first time someone publishes a polished report without thinking about styling.

Open or closed by default - and bookmarks

You can decide whether the Filters pane is open or collapsed when a user first opens the report. For most consumer-facing reports, we collapse it by default. The reasoning: if your report is well-designed, the most common filters should be visible as slicers on the page itself, and the Filters pane is for advanced or less frequent use.

For analyst-facing reports where users genuinely live in the filter pane, open it by default.

The bookmarkable state of the pane unlocks a few advanced patterns. You can build a "Reset filters" bookmark that returns the pane to a known state. You can build navigation bookmarks that close the filter pane when entering a focus view. You can even build guided tour bookmarks that progressively reveal filter complexity. These are nice-to-haves for most reports but show up in genuinely high-end Power BI work.

Rename filters for the end user

The display name of a field in your model is often not the right label for an end user. Your model might have a field called dim_customer_segment_lookup_key_segment_name because of how your data warehouse names columns. Your users want to see "Customer Segment".

Double-click the filter card title to rename it. This only changes the label in the Filters pane, not the model name, so your DAX measures and other report logic are unaffected. We use this routinely on engagements where the model is owned by a data engineering team and the report is owned by a business team. The model is technical, the report is human.

Search the Filters pane

If your report has more than ten filter cards, turn on Filters pane search. It is on by default in current versions of Power BI but worth checking. The search field sits at the top of the pane and lets users find a filter by name without scrolling through everything.

For reports with lots of filters by design (think operations dashboards or detailed analyst tools), search is essential. For reports with five filters total, it is overhead and adds visual noise. Use judgement.

The thing most teams get wrong

If you take one thing from this post, take this. The Filters pane is part of the user experience of your report, not a developer admin panel. Treat it the same way you would treat any other UI surface in any other piece of software.

The reports we see that work best at Australian enterprises have curated filter panes with five to eight visible cards, locked scope filters where appropriate, hidden cleanup filters with documentation, a colour scheme that matches the report, and applied cards in an obvious brand colour. The reports that struggle have the default grey pane with forty cards including every internal ID in the model.

This is a low-effort, high-impact area to focus on if your Power BI reports feel close-but-not-quite. If you want a second opinion on your reporting standards or you are setting up a Centre of Excellence and want to bake good patterns into your templates, get in touch. We have done this kind of work across dozens of Australian organisations and the patterns are pretty consistent.

The full Microsoft reference for formatting filters in Power BI reports is worth bookmarking if you want the exhaustive list of options. The post above covers what actually matters for real reports.