Piyush Dhameja on 14 Sep 2016 13:09:18
Add security to show/hide any specific page (Tab) on a report based on users privileges / Roles.
Administrator on 18 Apr 2024 09:59:22
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.
- Comments (614)
- Merged Idea (8)
RE: Page (Tab) level Security.
Love this feature.
RE: Page (Tab) level Security.
This option would certainly be great. Many end users are confused by empty pages that are obviously filtered by the role they have.It was an excellent contribution.
RE: Page (Tab) level Security.
This is core functionality that any leading dashboarding tool should be able to support.
RE: Page (Tab) level Security.
Its a no brainer win for Microsoft! Huge kudos if this gets finally added after demand for it since day one. It must be a top question asked by everyone I know who uses/consumes anything PBI.
RE: Page (Tab) level Security.
Six years later... still waiting.The new Audiences feature could be used as a work-around if you're willing to split your report apart so each page is it's own report, and then including them all in an app that utilizes Audiences. It's a pretty clunky work-around, especially if you have any measures or DAX expressions that would then need to be duplicated and maintained across multiple reports... not a good option. But I guess if, in a given use case, you don't have any DAX measures, then maybe this would be an option.Hard to believe this has been an idea for 6+ years and has worked it's way into the top two voted ideas with well over 9000 votes (and countless "merged" ideas) and still hasn't become a real feature... instead all we have is (now) two cumbersome work-arounds. C'mon.
RE: Page (Tab) level Security.
Pls implement this! :-)
RE: Page (Tab) level Security.
Implement this ASAP. Please!
RE: Page (Tab) level Security.
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".
RE: Page (Tab) level Security.
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 ;) )
RE: Page (Tab) level Security.
Please implement this Microsoft, users waiting since 2016..! > H E L P ! !