Give workspace admin(s) the ability to create custom roles for access to specific artifacts within the workspace and include the ability to control what each role has the ability to do within each artifact. For example, role 1 could have access to view warehouse & lakehouse but not edit them. Allow for the use of groups within each role as well to reduce overhead for workspace admin(s).
Also update how the ownership of certain artifacts within the workspace function. There are too many dependencies created when an individual user becomes the owner of all of the artifacts within the workspace. All artifacts should be owned by the workspace or the workspace admin(s) (or a custom role set by the workspace admin)
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v20 minutes agoCommunity ChampionNew606Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v7 hours agoCommunity ChampionNew12Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019711 hours agoFrequent VisitorNew6Views0likes0Comments