Support the ability to create a workspace under another one, inheriting it's permissions. Then allow this sub workspace to refine the permissions, etc. If users have access to the parent and the chi...
Jonnie_Coffee
6 years agoNew Member
As time goes on, we keep adding reports to our workspaces. It is getting to be quite cumbersome to navigate to specific items. Creating another workspace just for organization creates administrative overhead that I don't think is necessary. Organizational hierarchies would help alleviate this mess. The permission inheritance described by OP sounds like it would be sufficient.
Recent ideas
Metadata-Driven Copy Job Control at Table and Column Level
We currently achieve metadata-driven table and column selection in Copy Data activities by using dynamic queries. This allows us to dynamically determine which tables and columns should be processed ...Motasim094 hours agoNew MemberNew6Views0likes0CommentsDynamic ForEach Parallel Batch Count Based on Runtime Capacity
We would like Microsoft Fabric Data Factory to support dynamic configuration of the ForEach activity's parallel batch count at runtime. Currently, the ForEach batchCount is effectively configured as...Motasim094 hours agoNew MemberNew4Views0likes0CommentsMake Workspace-Level Surge Protection Limit Visible to Workspace Users
Please make the applicable workspace-level surge protection limit visible in the workspace settings. Currently, when surge protection is applied by Capacity Admins, workspace users don't get visibil...frithjof_v7 hours agoCommunity ChampionNew27Views2likes0CommentsAllow Custom Recipient Settings for Gateway Expiry Notifications
Now, during the final 90 days before the gateway version end-of-support date, operations continue, but semantic model contacts users can receive warnings in email The warning message is: "The on-prem...YuanMao8 hours agoNew MemberNew8Views1like0Comments