Share Dataflow Ownership with Workspace Admins
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
32 Comments
- 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.
Recent ideas
executeDaxQueries-like API call with effectiveUserName on SSO-enabled model with Service Principal
Please provide a way for a service principal to execute DAX - with an effective user name - against an SSO-enabled directlake semantic model and get per-user results that respect lakehouse OneLake Se...
