Insights / RLS in Power BI / Part 19
Part 19 of 20 · Audit itHow to audit who sees what in Power BI
The problem. You set up RLS months ago. Since then, people have joined, left and changed teams. Is it still right?
An RLS audit checks five layers.
| Layer | Question | Where to look |
|---|---|---|
| 1. Workspace roles | Who skips RLS? | Workspace → Manage access Service |
| 2. Model permissions | Who can build on, or write to, the model? | Semantic model → Manage permissions Service |
| 3. Role rules | Does every role have a clear rule? | Manage roles, TMDL view or Tabular Editor Desktop |
| 4. Role members | Who is in each role? | Semantic model → Security, then each group in Entra |
| 5. Security table | Who does the table give access to? | Query it Desktop |
Look for:
- Admin, Member or Contributor given to people who only read reports
- Build given to people who don't build reports
- A role with no rules (it shows every row)
- Individual people as role members instead of groups
- Leavers, and people who changed teams, still in groups or the security table
The habit: do this every month, and save the results so you can compare with last month. The free audit notebook (How to check it) does all five in one run.
Check before go-live
- Monthly audit done and saved Notebook
- Leavers removed from groups and the security table Service
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.