Separate settings for Export Data and Build Permission

[chaz2jerry1]

The current setup of Build Permission is too extensive and I see a need to find a middle ground in terms of data access permission. What I (and I assume others) need is a middle-level configuration where users cannot build new reports on the dataset (including analyze-in-excel), but can still use Export to Excel based on pre-configuered visuals. This way the developer can control what data granularity or filter 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. Related post in the Issues forum: https://community.powerbi.com/t5/Service/Export-Data-from-Visual-without-Build-Permissions/m-p/734470#M71708 Related Idea for analyze-in-Excel: https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/20487199-disable-analyze-in-excel-feature-without-disabling https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/34275706-tenant-settings-export-data

[pbiideas1]

This idea could've been worded a little bit simpler, but yes, requiring access to the entire dataset in order to export data that the dataset owner has placed in a visual for the user to see is beyond poorly thought out.

[vinod_dhanabala]

'I think Power BI Functional Design team should look into and consider a number of SSRS Portal functionalities meant for end users. +1 Vote. An option somewhere for dataset owners to enable or disable 'Export Data' based on the need and separate it from Build Permission. https://community.powerbi.com/t5/Service/Any-other-alternatives-for-Power-BI-Apps-Users-to-export-the/m-p/735876#M71847

[pbiideas1]

I'm part of a large enterprise organization. If I give people Build access, they'll have access to a ton of sensitive information. All I need is for people to have the ability to download the excel file associated with the dataset

[Peter_Dey2]

Currently if you turn off 'Analyze in Excel' in the Admin Portal this doesn't have any effect unless you also turn off 'Export Data'. Turning off 'Analyze in Excel' stops Paginated Reports from working. Turning off 'Export Data' stops you using shared datasets. If you leave these settings on and turn off the Build permission in the Workspace this doesn't have any effect on people with existing 'read' permissions who now have 'build' permissions even with this workspace setting turned off. It's a very confused set up where everything is interlinked and the descriptions for the Admin Portal controls are totally inadequate. There's a huge difference between having access to a dataset with multiple tables and columns that are not included in the report and being able to download a pre-defined table from a report.

[chrisu1]

This is also an issue with paginated reports. Users cannot view them without build, and paginated reports cannot be built without the columns/data fields being visible.

[Ouhs]

Also, stop granting user built permission by default, this option should be oped in rather than out.

[bola_labulo3]

I agree with this and it is urgently needed. It doesn't make sense to limit end users in this way especially as they previously had this function. My organisation uses Power Bi for management accounts, giving users build access would be giving them access to sensitive information they shouldn't see. "Export to excel" is one of the most basic features that all users would expect to be able to do. It's quite akward explaining that this function isn't available to them on a microsoft product.

[me10]

I'm sure it wasn't possible for my users to access the full dataset, while still being able to export summarised data from visuals, previously... Perhaps I'm mistaken. Either way, I'm really surprised this isn't one of the top issues!

[wieengels]

Hello, Could I ask please how likely is this idea to be implemented? It really limits the self-service experience, and adds a lot of security risk if end-users need build permission to export underlying data for a particular report or visual. It kind of defies the purpose of having the "export underlying data" option for end-users available in Power BI reports in the first place. Thank you!