Insights / RLS in Power BI / Part 7

Part 7 of 20 · Build it

Static vs dynamic RLS in Power BI

By Zohal Zahir · November 2026 · From the series Who sees what: RLS in Power BI

Say your sales data has a Region column. Alice should see North. Bob should see North and South.

Static RLS: one role per group. Make a North role ([Region] = "North") and a South role ([Region] = "South"). Add Alice to North, and Bob to North and South. New region → new role, then republish the model.

Dynamic RLS: one role plus a security table. Make one role, [Email] = USERPRINCIPALNAME(), and keep a table of who sees what: one row per person and region. Everyone goes into that one role. The table decides what each person sees. New region → add a row. No new role, no republish.

Email Region
alice@contoso.com North
bob@contoso.com North
bob@contoso.com South
-- static
[Region] = "North"
-- dynamic
[Email] = USERPRINCIPALNAME()

When to use which:

  • A few groups that rarely change, or two or three fixed audiences → static
  • Many users, access that changes often, or you never want to republish just to change access → dynamic
  • External guests or identities that change → dynamic (the table absorbs the change)

Static keeps "who sees what" in roles. Dynamic keeps it in a table.

Check before go-live

  • You chose static or dynamic on purpose, for this audience Desktop
  • Someone owns the security table and keeps it current (Part 19)

Want a second pair of eyes on your own model? The RLS review checks your roles, relationships and workspace access against this checklist, at a fixed price.

Found this useful? Share it.Tag Zohal Zahir on LinkedIn so she can say thanks.

Want your RLS checked on a real model?

Book a free 30-minute call. Tell us how your model and workspaces are set up, and we'll tell you where access could leak and what fixing it would involve.

Book a free call30 minutes. Reply within two business days