Miles Cole on 07 Mar 2019 02:57:43
Just like outstanding requests to assign app/workspace permission at a folder level within the app, we need to be able to give some users access to just individual dataflows without giving them access to the entire workspace that the dataflows are contained in.
- Comments (25)
- Merged Idea (1)
RE: Dataflow Permissions
It's been five years since the first idea came out. --And it's still pending. Please Microsoft, the permission to a specific Dataflow absolutely would help in specific project/department.
RE: Dataflow Permissions
We have created central master data dataflows to be shared across all workspaces. Unfortunately, It is not possible to grant permissions directly on the dataflows. The only way to make them available it to grant Contributor access on the Master Data workspace. This is an obvious issue as anyone could break or delete the dataflows. Microsoft, can you please add permissions to dataflows, similar to datasets?
RE: Dataflow Permissions
Adding a comment in the hope it will bump this somehow!This would massively increase the usefulness of Dataflows for us...simplified version of our situation = IT managed Dataflow in it's own Workspace exposes all data from a source, we then give the Data Owner Viewer access to that Workspace. What we want then is for the Data Owner to be able to create their own Linked/Computed Dataflows to expose parts of the data to other Business Users as they see fit. At the moment we have to create a Workspace per dataflow that they create, will get messy quickly. Would be much more effective if the Data Owner could create all of their dataflows in one workspace and manage permissions at the Dataflow level.
RE: Dataflow Permissions
What is the current status of this?
RE: Dataflow Permissions
Can't believe this is still here unactioned. Having to create workspace for exactly 1 dataflow is just stupid, lol. How can we get this elevated?Sometimes doing the right thing is important regardless of the number of votes an idea gets in some system.
RE: Dataflow Permissions
YesRead-only-user can also access to dataflow ,I don't want that.And different department member-user need get different permissions
RE: Dataflow Permissions
Similar to the 'Build' permission for datasets, It would be very useful to be able to manage access to dataflows at the individual dataflow level.
Currently, it is only possible to grant access to consume a dataflow by granting at least 'Viewer' permissions to the whole workspace that contains the dataflow in question, which has the undesired effect of opening up any other dataflows to the added user. The only workaround for this is a dedicated workspace for each dataflow (or a set of common access dataflows).
Whilst the workaround does provide the functionality required, it results in a much more complex and crowded Power BI estate for a Power BI Administrator to manage. Having the 'Build' Permission available, would enable a much less complex, and concise Power BI estate.
RE: Dataflow Permissions
Agreed, dataflows and datasets ingest and expose data in much the same way, so the security architecture should be in parity across the two. Published dataflow best practices seem to be in conflict with each other because of this, and I don't see why you wouldn't want dataflows to be treated as separate securable objects
RE: Dataflow Permissions
The viewer access should also provide view access to the list of dataflows in the workspace. Currently this is only achieved by providing member or contributor access, allowing them to edit, which goes against the objective of them being able to only 'view' the dataflow.It would be beneficial for the viewer role, to show the dataflows within the service, along with details as to errors and last refresh time.