Row-level security

Rules in the semantic model that limit which rows each user can see.

Row-level security lets one report serve every region, team or client, each seeing only their own rows. Done well, it replaces a pile of copied reports. Done badly, it leaks data or slows every visual.

Part of the Model layer of the ecosystem. Reviewed 13 November 2026 by Piyush Jain.

What Row-level security is

RLS is defined in the semantic model as roles. Each role has DAX filters on tables, such as Region = "West". Users or groups are added to roles in the Power BI service, and every query they run is filtered by their role.

Static rules hard-code the value per role. Dynamic rules use USERPRINCIPALNAME() to look the user up in a security table, so one role covers everyone and access is managed as data. Object-level security goes further and hides whole tables or columns.

See it work

Rebuilt on demo data from the patterns in my own reports.

RLS Pattern Kit
Home checks the email, finds the person in the roster and opens their page: My team for Leo (manager), My accounts for Sam (rep). Same file; RLS keeps the rows to their own.
The hierarchy role keeps every roster row whose path contains the signed-in email.

Source: demo data (Meridian Goods)

When to use it

Use it when

  • Several audiences need the same report but must not see each other's data.
  • You are about to copy a report per region or client. Use RLS instead.

Think twice when

  • Avoid relying on RLS for people with edit rights to the workspace. Admins, Members and Contributors are not filtered by it.
  • Avoid it as the only control for highly sensitive data that should not be in the model at all.

The mistakes I see most

From opening other people's models. Each one is fixable.

  1. 1

    Testing as yourself

    As the model owner you see everything, so the report looks fine. Use View as role in Desktop and Test as role in the service, with a real user from each group, before go-live.

  2. 2

    Filtering the fact table directly

    Rules on a large fact table are evaluated on every query. Filter a small dimension or security table instead and let the relationship carry the filter. It is faster and easier to reason about.

  3. 3

    Forgetting workspace roles

    Giving viewers the Member role 'so they can see the report' switches RLS off for them. Share reports through an app or with Viewer access.

Questions people ask

Does row-level security apply to workspace admins?
No. RLS filters only users with Viewer access, or people the report is shared with. Admins, Members and Contributors of the workspace see all the data.
What is dynamic row-level security?
A single role whose DAX filter uses USERPRINCIPALNAME() to find the signed-in user in a security table, so each person sees only their rows and access is managed by editing that table.
Does RLS slow down Power BI reports?
It adds a filter to every query. On a small dimension or security table the cost is small; complex rules on large fact tables can slow every visual.

Sources: Microsoft Learn: Row-level security with Power BI. Opinions are my own.