Insights / RLS in Power BI / Part 18

Part 18 of 20 · Share it

6 things Power BI RLS doesn't hide

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

RLS filters rows inside the model. Anything saved in the report, hidden from view, or copied out needs its own fix.

  1. Saved slicer and filter selections. A saved selection can show a name or value. Clear sensitive selections before you publish.
  2. Typed titles and text boxes. Typed text isn't data, so RLS can't filter it. Keep names and numbers out; use measures for dynamic titles.
  3. Hidden columns. Hiding a column isn't security. People with Build permission can see it. Use OLS (Part 8).
  4. App audiences. Audiences choose which reports appear. RLS still decides which data shows.
  5. Exported files. RLS filters the export, so the file holds only that person's rows. But if they forward it, whoever opens it sees those rows. Use sensitivity labels so protection travels with Excel, PDF and PowerPoint exports.
  6. Publish to web. It makes a report public to the whole internet, and it doesn't support RLS. Ask your admin to restrict who can use it.

The rule: secure the data in the model. Treat everything in the report as visible to anyone who can open it.

Check before go-live

  • No sensitive values in saved slicers, titles, page names or text boxes
  • Sensitive columns use OLS, not just "hide" Desktop
  • Sensitivity labels are applied to models with sensitive data
  • Publish to web is restricted in your tenant

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