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 (609)
- Merged Idea (8)
RE: Page (Tab) level Security.
A must have, even the ability to expand the report pages in audience setup and hide/unhide certain pages based on audience.
RE: Page (Tab) level Security.
this is so necessary
RE: Page (Tab) level Security.
The workaround is not secure. Once someone has the URL to a hidden page, they are able to see the content so not a viable option.We need real page-level security. Please consider this feature important enough for prioritization. My only alternative at this time is to start making separate reports and publishing them in an app with report-level security. It requires me to maintain several reports (and potentially data models) instead of 1 which is a pain.Thanks
RE: Page (Tab) level Security.
Yes please do add this, it's quite inefficient to have to duplicate my work across multiple versions of a report because I cannot implement any actually secure way with Page Level Security.
RE: Page (Tab) level Security.
Workarounds still won't cover Page Level Security requirements like if user has an access to report & have a link even navigation hided user can get the page with link.
RE: Page (Tab) level Security.
It seems essential to be able to filter on page level of a report by audience. RLS feels quite clumsy and it is not a solution, but a patch at most.
RE: Page (Tab) level Security.
This would be a great add. At the moment I work with several reports, but it is just time consuming and not efficient!
RE: Page (Tab) level Security.
This would be a great add!!
RE: Page (Tab) level Security.
Just add a simple "show this page/tab" based on a defined value type security option should be simple enought. RLS and conditional page navigation is a pain to set-up, timely and has limitations - even the fact that the who rows would need to be checked. In Excel you have had hide tab for about 15+ years, if the page on a report is hidden based on Username or a set value - its a quick way to block someone seeing it or physically clicking on it. Then you do not need any fancy rules for RLS evalutions, just a simple bit that checks if they active user is on the guest list.Even better if a visual could have a simple "show/no show" option that can be set by a parameter too.
RE: Page (Tab) level Security.
A related need to this, that may be easier to accomplish, would be to enable page-level visibility toggles when publishing to an "App" - currently it only allows you to hide/show an entire report with all pages.