MergeStatus.txt (0.20KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.19KB) MergeStatus.txt (0.19KB)
Comments
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
Please Microsoft,
Do something about this as we have been waiting for the past 5 years for this Page Level Security
Creating multiple pages also wont suffice the requirement here consider below scenario:
we achieved navigation by using custom formatting of page navigation and users navigated to relevant pages on Published version based on their roles . what if
"page A user capture the URL information for Page A and shared URL to another user who should not supposed to access Page A since User B is also part of RLS so he also able to access content in Page A on the time user access the URL since no Page level restrictions are there but Page A was not created for User B".
Thanks
This should be standard feature for Power BI by considering sensitive information which we are exposing and target audience which will access those information.
By adding this feature , we can avoid creation of multiple reports based on sensitive Data and relevant audience which will consume those information.
This is important feature for my organisation.
Is any update on whether it is actually being worked on rather than just "Under Review"?
How is that not a standard feature?
I too need and vote for this Pbi Page level security feature. When can it become standard in the product? Thanks.
This should be standard behaviour. Hopefully it will be there soon. Don't know how long it's under review unfortunately.
Dear Team,
I am in urgent need of Page Level as well as Column Level Security in Power BI Desktop. I worked a lot on Row Level security but RLS is not applicable when Users want us to hide entire page or a particular column.
If this features get add, life will be easy.
I have used the requested features in Oracle BI and so good.
Thank you,
Charu
Please add page level security feature in Power Bi.
Administrator on 3/30/2022 2:13:14 AM
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:
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:
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.
Next, you can create a page navigation button and click the fx button to conditionally format the destination based on the column:
Now the button can navigate the user to the selected page: