I'm sure I'm not the only one who's struggled to either set up complex RLS and/or OLS rules to govern access. Certainly for design of product that are intended as a 'one stop' for multiple users in large organisations.
One of these aspects is the hierarchies of precedent from the access groups. As a 'catch all' I use our groups 'ALL USERS' initially - however, there are certain groups I would like to grant additional or limited access which are based on distribution lists. As the 'all users' is a broader group - it naturally takes precedent in the semantic model without the ability to control which group / user is treated first.
Similarly - within the dashboard model - there isn't a way in which to set an order of precedence for different roles to be treated.
I believe applying something like this as part of a model rather than complex coding might be a game changer for many report designers and user access management teams that struggle with the complexities especially in large organisations.
Thanks
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections