As we rolled out the preview of Shared Datasets and the new Build permission, we received feedback that ourย limitationsย onย export of summarized dataย from a visualย areย overly restrictive.ย ย
Today a user with Read permission can see a visualโs data in two ways. First, they can see it rendered in the visual. Second, they can use the See Data feature to view a grid of the data used to render the visual. The grid contains only the summarized data.ย
As such the user has access to the summarized data for a visual already.ย Before theย recent permission changes to introduceย the Build permission,ย users with the Read permission wereย alsoย able to exportย theย summarized data fromย theย visualย to a CSV file.ย With theย changes after Buildย was introduced, export summarized data required Build permission even though users could still access the same dataย as described above.ย
Weย areย adjusting our approach based on your feedback.ย Specifically, we will allowย users with the Read permission to export summarized data from a visual.ย ย This change will be rolling out over the next week.
Exporting the underlying data for a visual will continue to require Build permission.ย The underlying data is the detailed rows that were rolled up to show in the visual. This ensures that consumers do not export more data than the report is showing them.
For organizations needing a truly locked down data export experience, we offer severalย existingย controls:
- The report author can fully prevent any data export, can allow exporting only summarized data, or also allow export underlying data for users with the Build permission.ย
- Theย Power BIย adminย can control which users canย export data across all content in Power BI. This can be used to lock down all data export experiences.