Manage Security Roles from A Report

[Jos1986]

We have numerous reports that link to a particular semantic model. This semantic model limits the user to only seeing data for accounts they own. However, one of these reports is a heat map, and we'd like for reps to see the full map - not just the portions connected to their accounts. I'd hate to splinter our semantic model into two versions to manage simply to accomodate for a single report. Any ideas on how to approach this?

[Anonymous]

Hi @Jos1986 ,

Based on the description, copy the heat map report to a new workspace and don’t apply the row-level security. Then, ensure users who access to the heat map are members of the new workspace. You can share heat map report with others.

Share Power BI reports and dashboards with coworkers and others - Power BI | Microsoft Learn

Best Regards,

Wisdom Wu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Jos1986]

I made a copy of the report and moved it to a new workspace. I then opened the report in desktop, in attempt to remove row-level security. On the modeling tab of the report, the manage roles option is grayed out. I assume this is becase we use a live connection to the dataset. And that dataset controls access.  I feel like this puts me back in my original predicament of possibly needing to create a second version of my dataset. Is there any way to ensure row-level security is not applied without changing the dataset?

[Anonymous]

Hi,

When using a live connection in Power BI, the security (RLS) settings are inherited from the data model and managed in the dataset.

Try to create a role that allows full access to the map data.

You can view the following documents to learn more information.

Dynamic row-level security with Analysis services tabular model - Power BI | Microsoft Learn

Solved: RLS with Live connection to semantic Model in Powe... - Microsoft Fabric Community

Plan for reporting - Configuration Manager | Microsoft Learn

Best Regards,

Wisdom Wu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[audreygerred]

Hi! You could create another table with aggregated data so that you can still create the map (i.e. aggregate at whatever level you are mapping on, i.e. zip, state, etc), but do not apply your RLS filtering rules to this table that will be used for the map. For example, if you have a sales person tables with a relationship to your fact table and the filter is on the salesperson table, when you make the new summarized table, do not join it to the salesperson table.