Forum Discussion
Export Data from Visual without Build Permissions
Thank you for the suggestion to implement Apps as an additional layer but this still does not solve my security concern. I am able to share through an App but the Export Data Option for a visual still requires the BUILD permissions assigned to the user on the datset to work. If I have this permission granted and the tenant setting "Use datasets across Workspaces" enabled then the user could simply start a new Power BI report in Power BI Desktop source this dataset and see the underlying data.
Why does the report allow us to specify the export of summery OR export of underlying data if this new "Use datasets across workspaces" feature is just going to circumvent that by allowing users to pull the datasets into Power BI desktop regardless.
Thanks!
Hi Anonymous
It seems you create an new App workspace.
What i refer to is classic App workspace.
Best Regards
Maggie
Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
So what you are saying is that in the NEW Workspace Experience what I have experienced with the Security is the expected result. However, if I were to create a classic workspace this would be mitigated by working as designed prior to this update?
Thanks!
I have same concern and challenge with the OP, that the current setup of Build Permission is too extensive and need to find a middle ground in terms of data access permission. What I (and I assume others) need is a middle configuration where users cannot build new reports on the dataset, cannot use Analyze-in-Excel function (same as building new reports), but can still use Export to Excel based on pre-configuered visuals. This way the developer can control what data granularity is available to the consumers.
This ties in to existing requests to disable Analyze-in-Excel feature specifically, and now expands into the broader scenario of Build Permission and shared datasets.
I concur that the build permissions is too extensive. There needs to be an option to allow users to read and export to Excel, without giving them permission to build their own reports.
