MergeStatus.txt (0.20KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.18KB) MergeStatus.txt (0.19KB) MergeStatus.txt (0.19KB)
Comments
Page (Tab) level security is basic necessity to minimize the cost otherwise have to build separate report with out that page (Tab). Please make it available soon.
Yess
This is a much needed function, it would allow one model, one refresh to be shared among several users. It would increase efficiency 100% and limit the number of model and refreshes that we need some.
Any update on this feature?
When this function will be available...??
This is a much needed function, please surprise us Microsoft!
This is a very desirable behavior needed in PBI.
Add ability to select which report pages or even better specific visuals you want to apply row level security with.
This cannot miss in a BI tool! Waiting for it!!!
I am really desperate for this ,
One more thing please give columns level security on table and column matrix.
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: