MergeStatus.txt (0.20KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.19KB) MergeStatus.txt (0.19KB)
Comments
The current alternative of creating a separate report for each user group is backwards and dangerous to the point where I'm not going to use Power Bi for this. Really would appreciate a solution.
Urgently need this!!!
we really need this security option.
This is much needed when we deal with RLS. Please act soonest possible.
Hello guys, thats a very old issue. Where are we going here?
Why I need to do the pages in a lot reports again and again to hide specific pages to some roles? Thats not useful for senior developers.
This would be really useful.
Urgently needed :(
Any ETA on this?
what is the alternative/workaround while waiting for this feature? Is it to have a PBI per role/profile?
Please do this. It's a huge priority.
This would a massively helpful feature, please add this.
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: