Forum Discussion
Help organizational hierarchy RLS
yes, we have a rules table that is controlled by the business. It is mostly based on ActiveDirectory but allows for overrides. That table is then matched against USERPRINCIPALNAME in the RLS rule.
Treat your access permissions as lists
Selma = {1,2}
Then in your RLS rules you can test against these lists
Department Level 1 in {1,2} => Selma is permitted
This is on me for not mentioning it before, but an approach like that wouldn't work if I have 60 of those cases, which I have.
Why would that not work? We have similar implementations with hundreds of such rule sets.
But then you have hundreds of manual lines? Can you talk me through this implementation more because now I feel like I'm missing some vital information.
You set up a rule with the DAX editor of the RLS implementation, do you use USERPRINCIPALNAME()?
So Blair should also have access to deparment 1.1.1 because that belongs to 1.1 and Selma has access to all there. How do I set it up step by step?
Level 1 in what exactly, do I need to give a list with a hundred items or can I use a VALUES() here and how does the USERPRINCIPALNAME come in?yes, we have a rules table that is controlled by the business. It is mostly based on ActiveDirectory but allows for overrides. That table is then matched against USERPRINCIPALNAME in the RLS rule.