Forum Discussion
Export Data from Visual without Build Permissions
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.
Yes, exactly this. I would like "Export to Excel" treated separately from "Build" permission, because "Build" raises massive security concerns whereas "Export" is easy to control.
