Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hello,
I am building HR reports that have an underlying dataset containing highly sensitive personal information.
I want the report viewers to only be able to see the visuals with aggregated data (like averages, ratios ...) - with no possibility to view underlying un-aggregated data.
I already know about 3 ways viewers can access this data:
My questions: Are there any other ways for viewers to see underlying unaggregated data? And how to disable it? How do you deal with this situation?
Warm regards,
Jakub
Solved! Go to Solution.
Hi, @jdusek92
As mentioned in service-datasets-build-permissions ,
Power BI provides the Build permission as a complement to the existing permissions, Read and Reshare. All users who already had Read permission for datasets via app permissions, sharing, or workspace access at that time also got Build permission for those same datasets. They got Build permission automatically because Read permission already granted them the right to build new content on top of the dataset, by using Analyze in Excel or Export.
With this more granular Build permission, you can choose who can only view the content in the existing report or dashboard and who can create content connected to the underlying datasets.
You can remove Build permission. If you do, the people whose permissions you have revoked can still see the report, but can no longer edit the report or export underlying data. Users with only read permission can still export summarized data.
You need to check the dataset permissions and remove build permission for the specified user to restrict their access to the underlying data source.For reports related to datasets, they will also be restricted from using Analyze in excel, export data, download pbix...
Best Regards,
Community Support Team _ Eason
Hi, @jdusek92
As mentioned in service-datasets-build-permissions ,
Power BI provides the Build permission as a complement to the existing permissions, Read and Reshare. All users who already had Read permission for datasets via app permissions, sharing, or workspace access at that time also got Build permission for those same datasets. They got Build permission automatically because Read permission already granted them the right to build new content on top of the dataset, by using Analyze in Excel or Export.
With this more granular Build permission, you can choose who can only view the content in the existing report or dashboard and who can create content connected to the underlying datasets.
You can remove Build permission. If you do, the people whose permissions you have revoked can still see the report, but can no longer edit the report or export underlying data. Users with only read permission can still export summarized data.
You need to check the dataset permissions and remove build permission for the specified user to restrict their access to the underlying data source.For reports related to datasets, they will also be restricted from using Analyze in excel, export data, download pbix...
Best Regards,
Community Support Team _ Eason
Hi @jdusek92 ,
In addition to what you have stated, in the Service you have to make sure to not select these options as well when you share the workspace/report. In fact, for HR reports, we usually only share the APP and keep it locked down. For example, the APP might look like this (we also share only with individual is possible so we know who has access and nothing is selected so they can't share or get to underlying data. And then, we make sure that the workspace/report is not sharing either.
This is the APP:
You may also consider RLS if you really want to get it tightly regulated.
To clarify though - if you directly share the .pbix file with users, they will almost surely get to all the underlying data and that is why you should stay in the Service for this type of report.
Proud to be a Datanaut!
Private message me for consulting or training needs.
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
86 | |
46 | |
25 | |
21 | |
19 |