8 Merged Ideas
Comments We need this fix ASAP! @Microsoft
I have achieved this using RLS and Page navigation. I did the RLS for Product names in table then took same product as the Navigation. Now it shows only the products assigned to the particular users...
I hope that "Under Review" is a good sign. This is a really important feature that I'm sure will be very popular. The workaround that you posted is easily hackable. When you're dealing with Sales people and commission info, security should be the priority. In my report, I already have RLS security set up and only those salespeople assigned to certain regions can see their regions. That's good. However, there are pages that don't apply to them and it's a big issue having to create 2 separate reports. That doubles the maintenance!
What is so terribly hard about this? At a basic level, the only functional improvement that needs to be added is to enhance the Permissions model at the page level. This allows for the existing Report/App level permissions to remain, and within that permission scope each page can be assigned specific permissions, with the report/app level scope set as the default.
This doesn't require any changes to the existing RLS model, so that a page that has RLS continues to work as currently implemented.
This model would also keep the same security context whenever a report is exported to PPT, PDF or Analyzed in Excel.
Omar como solucionaste este tema?
Gracias
Leo A
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"?
Administrator on 7/22/2022 8:30:01 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: