Dataset Best Practices - Using reports in multiple Apps against a dataset

[kozmar]

We have created datasets that have popularity across the organization.  

I'm looking for some best practices we can implement on how to mange this, especially with security. 

I'm thinking I use one workspace for my datasets that have interest across the organzation, and publish this as an app to the entire organization having access.  The dataset will not have any real reports, just datadictionary information available.  

Then grant build access to my power users, for build persmissions on this dataset, and expect they can create their own reports in their own workspaces/apps for whomever they like. 

Will this work, Any other ideas/suggestions how to manage this?  The security management is getting out of hand... 

Thanks so much!! 

[Watsky · Accepted solution]

Hi @kozmar,

Is the issue that you want users to have access to only specific data but that data is all in tables where there is data the users should not have access? If so, my thought is to use dataflows.

Dataflows act like data warehouses so you can:

• Pull in all the relevant data,
• Exclude the data you don't want users to have access to,
• Format the data for all users, 
• Allow users to pull from the dataflow instead of the data source itself which will mean only one request to the data source would happen for the dataflow. The users requests would hit against the data brought into the dataflow on the Power BI service, and
• You could setup multiple dataflows if you wanted different groups of users to have access to different data.

An overview of dataflows across Microsoft Power Platform and Dynamics 365 products - Power Query | M...