Add security to show/hide any specific page (Tab) on a report based on users privileges / Roles.
Attachments: MergeStatus.txt (0.20KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.19KB) MergeStatus.txt (0.19KB)
Under Review

Thanks for all the feedback! Currently, Power BI does not have a security feature for pages; however, using conditional page navigation and RLS, you can create a custom navigation experience that shows different page options for different roles.

Here's an example of this custom navigation experience: 
 Navigate with a Go button

You can start by hiding all pages on your report except the landing page. Then you will create a column that contains the exact names of the pages in report.
Here's an example: 
Create a table

Using Power BI's row-level security feature, you can define the security roles and rules for this column, and then you can add the column to a single-select slicer.
The slicer will only show values in the column based on the security roles and rules that you've applied to this column.
Navigate slicer

Next, you can create a page navigation button and click the fx button to conditionally format the destination based on the column: 
Page navigation button
Now the button can navigate the user to the selected page:
Navigate with a Go button




Please add this functionality to the newly released audiences experience. Today we can only hide full reports.

For some use cases page level security is okay, even of the entire model is visible to the end user. Because the proposed work around also implies the end user has full access to the underlying datamodel. Also, if we copy entire datamodel and republish with only a subset of pages, the end user has full access to the underlying datamodel.

We get it. It's fine. Maybe call the feature "page level visibility" instead of "page level security" as indeed from a security standpoint it's a real hard issue to solve. Hiding pages doesn't really protect against data getting leaked. But maybe many votes just want "page level visibility".


This would be a beautiful extension to the Multiple Audiences (link) that has just gone to Public Preview!

Right now it's possible to hide or show complete reports, being able to do this on specific pages would be even nicer!

(now I'm going to make extra reports for different audiences, The logic I'll choose whill of course be perfectly clear to myself, but don't want to be in the shoes of the person who's ever going to need to make a fix or changes when I'm out of the office ;) )


Please implement this Microsoft, users waiting since 2016..!

> H E L P ! !


We also needed this feature as Business doesn't want to use an extra button to navigate to hidden pages as it is not user friendly and creates more confusion.

Hope this will be considered in future releases.


Not sure why this isn't at the top of Top ideas being as it has almost 9000 votes and the other highest is 3000 something. Feels like this idea is being hidden until people forget about it!


Please do consider below point before doing a public preview.

1. If report has “REPORT BOOKMARKS” user can still bypass the page navigation and access the pages. – Please give report authors to hike the “REPORT BOOKMARKS”.

2. Export to “PPT” – user can still bypass the page navigation and access the information.

3. Export to “PDF” – user can still bypass the page navigation and access the information.

So, we need a proper Page security so we can use single report/App for different department with Page security. Thanks


Any update if this will be added to the roadmap? The conditional navigation is a workaround, but doesn't provide a fool proof way to hide pages (export to PDF, PPT shows all pages; bookmarks bypasses this too)


That's a very important feature, please make it available as early as possible



This is a highly needed feature. I currently need to implement Page Level Security as a business solution, but it is not currently possible.

Developing multiple reports which maintain different views of the same data & measure calculations is a continual headache & waste of company resources. To constantly ensure that for any change made to any 1 of these reports, the same change must also be developed in all other reports, is the opposite of best practices. 90% of development must be done N times (for each report), rather than 1 time as it should be 1 single report.

If Microsoft could make adding this feature a priority, it would be GREATLY appreciated.


Nathan Vail


Does anyone have any idea when this will be available? Could really do with this functionality as our security team was able to break the work around within 5 minutes of me sending it to them.