Forum Discussion
Revoke RLS for a specific page
Hi,
I have my pbix with RLS implements based on the heirarchy of the organisation. The report has 6 tabs and the RLS is applied on all 6 tabs currently.
However I need to know if I can ignore this RLS rule for 2 tabs and keep it applied on remaining 4 tabs.
I know page level security is currently not available but is there a workaround for this?
Creating a new table with the page names is not a problem. Can do that.
However looking for a way to apply this new table to revoke RLS.
Basically if page 1 then RLS is applied.
If page 2 then there is no RLS.
The above requirement is very ideal and is the only pending requirement for my report.
v-diye-msftI thought of it but I require my users to export the underlying data as well. Anyways I have followed the similar approach but replicated the entire table ( 3 tables in my case). Marking this comment as a solution.
Greg_Deckler Please see the above.
10 Replies
Anonymous , I doubt you can apply RLS page wise. May you have summarized tables without RLS and use those
amitchandakI could have taken this approach but there is a requirement to allow my users to export the underlying dataset.
Anonymous You could potentially use this approach for your 1 page that you want to lock down, basically put duplicates of the columns in a separate table. https://community.powerbi.com/t5/Community-Blog/Column-Level-Security/ba-p/1309392
Greg_Deckler I dont think this will work when RLS is applied based on the userprincipalaname. So basically the users can see the data based on their logins or heirarchy. However I want to bypass this RLS which is based on username only for two tabs and allow every user to see all data in these two tabs.
I have users 'a' 'b' and 'c'.
Tab 1 to 4 -> user 'a' can see only data relevant to 'a'. and so on for other users too.
Tab 5 and 6 -> user 'a' can see all data including that of 'b' and 'c' and so on for the other users as well.
Anonymous Right, so the thought is to duplicate your fact table data and not have it connected to whatever table your RLS is tied to. But would need to better understand your model and data to see if it would work.
Hi Anonymous
Typically the way I have worked around this issue is creating a summarization table within the model. This table is disconnected from any tables that have RLS applied. By doing this, users can see summarized data but not the underlying data that comprises those aggregations.
v-diye-msftI thought of it but I require my users to export the underlying data as well. Anyways I have followed the similar approach but replicated the entire table ( 3 tables in my case). Marking this comment as a solution.
Greg_Deckler Please see the above.
