Description: Currently, Power BI provides robust Row-Level Security (RLS) to restrict data rows, but it lacks a native mechanism to restrict or hide entire report pages based on user roles or USERPRINCIPALNAME().
In enterprise environments, we strive to maintain a single .pbix file as a Single Source of Truth. However, certain pages contain confidential department-specific data (e.g., executive dashboards, HR metrics, or specific operational logs) that unauthorized users should not even be aware of or able to click on.
Current workarounds and their flaws:
Splitting reports into multiple .pbix files: Breaks centralization, increases maintenance overhead, and duplicates dataset refreshes.
Using RLS to blank out data: Leaves the tab visible, causing user confusion and support tickets because users think the report is broken.
Bookmark/button workarounds: Highly fragile, difficult to scale, and hard to maintain.
Requested Feature: Please implement native Page-Level Security (PLS) that allows report authors to bind page visibility to existing RLS roles or DAX expressions. Unauthorized users should have restricted pages completely hidden from the navigation bar rather than seeing empty tabs or requiring separated project files. This will greatly improve governance, security compliance, and user experience.
