Insights / RLS in Power BI / Part 2
Part 2 of 20 · Build itPower BI RLS leaky tables: how to find them
The problem. Your RLS filters five tables. Your model has seven.
Why. RLS filters one table. It reaches other tables only by travelling along relationships. Any table the filter can't reach is returned in full, to everyone in the role.
The usual two: a targets table related only to the date table, and a KPI summary table with no relationships at all. Both look harmless in model view. Both show the whole company to a user who should see one region. "View as" passes, because you check the revenue visuals, not the targets card.
The fix. Every table is one of three things:
- On the filter path: related, directly or through other tables, to the table your role filters
- Blocked with
FALSE()for restricted roles - A leak
There is no fourth option.
- If the table has a Region column at the right grain, relate it.
- If it doesn't and it's sensitive, block it with
FALSE(). - Never invent a key just to force a join.
-- on a sensitive table that can't be related
FALSE()
Date tables are usually fine to leave unfiltered. Check them anyway if they hold anything sensitive.
Check before go-live
- Every table is on the filter path, blocked with FALSE(), or not sensitive Desktop
- "View as" testing includes targets, budgets and summary visuals, not just sales
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.