Right now, having multiple people edit dataflows is not just a pain, but risky. Assuming the person trying to take over a dataflow has access to all the sources, it's a serious click tax to have to ...
We need to allow all admins of the workspace in which the dataflow is held to be able to edit the flow. Multiple people contribute to a dataflow at different stages of a project but all need to be able to review, understand and if necessary edit the dataflow
- Just a must have for team development, preferably like this: 1. Workspace Admins should have the same rights as the dataflow owner (Edit/ Settings/ Properties/ Refresh/ Export JSON/ Delete). 2. Members shall have read/write access only (Edit/ Export JSON). 3. Contributors shall be granted read access only (Can see all flows and their query steps (or M-code), but cannot change anything; may export JSON too) 4. Viewers shall have no access to dataflows
- Admins should be able to view, edit, etc. Viewers should be able to view code but not edit if using best practice of separate workspaces, should not be an issue as the only members should be involved in the development
- What if workspace owner same as dataflow owner.
- You can take ownership, but then it resets credentials, which breaks the whole thing
- I'm hesitant to report this as a BUG because I know it's going to come back as "by design" like several others I have reported. In this case, it is just POOR design. Kind of like how if you are an Administrator on a Gateway, you do NOT automatically inherit permissions to USE any Data Source defined UNDER that gateway. Oh sure, you can edit said Data Source and grant yourself those permissions. But really, why does it have to be that way?
- Absolutely vital to allow groups to edit a workflow, not just a single person!
- I need to enable people to make changes to the tables/queries within the dataflow. I set it up for them, but I'm not doing all of the work.
- Currently, only the owner can change an existing dataflow, no other user has access to it. What if that person leaves the company or is on vacation? This should be opened up for admins or members, preferably even with a read / write permission settings for a dataflow.
- Like with datasets, the workspace group should be the standard owner of dataflows and not the creator of the dataflow.
- At the moment, you can view or edit a data flow only if you are the owner. I would like either: - the ability to view the entities in a dataflow if I am not the owner without having to takeover the data flow - the ability for the owner of the data flow to be defined as a AD group rather than an individual
