---
title: "How dashboard filters and filter scope work | Oplema"
description: "Learn how a dashboard filter changes the rows a view includes, how its scope works across visuals, how it differs from a rule and how to test a conclusion."
url: "https://oplema.com/learn/business-intelligence/filters"
updated: "2026-11-04"
---

Lesson 11 of 15 · Lab

# Dashboard filters: scope, selections and limits

A dashboard filter lets a reader change which rows a view includes, without changing the rules behind it. Its scope decides which visuals on the page respond. Use one to explore a question, or to test how much a conclusion depends on one group.

Sales of 80 for A and 20 for B, filtered to B
| Visual | In the filter's scope | Shows |
| --- | --- | --- |
| Headline | Yes | 20 |
| Bars | Yes | B only |
| Headline | No | 100, beside bars showing B only |

The last row is legitimate if it's labeled as the overall total. Unlabeled, the page seems to disagree with itself.

At [fictional Vandelay Coffee Supply](https://oplema.com/learn/business-intelligence/what-is-bi), South leads North €5,900 to €5,578 in net value, and founder Max Thrust wants to place a hire on that basis. He asks you to take out customer Initech.

Initech is a South customer worth €3,000. Who leads without it?

North, comfortably. South falls to €2,900 against North's €5,578, so the lead rests on one customer.

## Remove each region's biggest customer

1. Select **Initech** in this live chart in [Vista](https://oplema.com/vista), Oplema's browser app for dashboards. The buttons now exclude what you select. Read the regions.
2. Select **Initech** again to bring it back.
3. Select **Starhopper**. Read North.
4. Select **Everyone** to clear the filter.

What each removal does

Without Initech, South is €2,900 and the total €8,478. Without Starhopper, North is €1,690. North depends on Starhopper even more than South depends on Initech.

## A filter differs from a rule

A preparation rule such as `status = 'booked'` applies to everyone, and it belongs to whoever owns the metric. A filter applies to this reader, on this page, for now. Keep them apart: a rule a reader can switch off has stopped being a rule.

A filter also gives no security. In Oplema, anyone who can view a published dashboard can reach its input data, whatever is selected. Don't use filters to hide rows from people.

## Common filter mistakes

- **No visible selection.** A number that excludes something looks just like one that doesn't. Label what's selected. This filter's own wording does that here.
- **No clear reset.** Readers should get back to the full population in one click.
- **Unclear scope.** Check which visuals respond before you compare them.
- **Comparing filtered totals with a full target.** A part of the business can't be judged against the whole company's number.

Use a filter when readers need to choose a group themselves. If everyone needs the same restriction, it belongs in [the flow, as a rule](https://oplema.com/learn/data-preparation/filter-rows).

## Filter scope in Power BI and Tableau

In Power BI, slicers filter the other visuals on a page by default, and report editors can change that per visual with **Edit interactions**. In Tableau, a filter starts on one worksheet, and **Apply to Worksheets** shares it with others. Check each tool's security rules separately. The SQL equivalent of a filter is one more `WHERE` condition, added for that reader alone.
