Hi @clarawang_12 ,
I have to mention that the row-level security in Power BI is all about the dataset. What does that mean? that means you define the security at the dataset level, not at the visual level. Using the row-level security, you cannot say this role has access to one page, and another role has access to another page or another visual.
now that the row-level security on the dataset cannot resolve this requirement, here is the way to do it: you can separate copies of your visuals into two different Power BI reports. but we don’t do it like a normal copy. every copy would be sourced from the shared dataset. the first step is to create a Power BI file to get data from Power BI dataset as you have seen above.
- Because in this method, the security is not implemented on the dataset, the user has access to the data anyways (unless you set up RLS). so if user creates their own report on the dataset, they can build whatever they want.
- The main benefit of this method is the usage of a shared dataset because the normal copy will create a big overhead of maintaining multiple reports and code logic. In this mode, the visualization is separated from the modeling.
Share Different Visual Pages with Different Security Groups in Power BI - RADACAD
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
