Forum Discussion
Row Level Security - assigning roles by groups
Hi all
I've been looking at Row Level Security and am trying to work out how it works with groups. There seem to be different types of groups that Microsoft use and I'm really not clear how to tell one type from another and which one(s) we use in my organisation.
Essentially, is is possible to define roles by teams? Is this done automatically (eg. on my calendar on Outlook the rest of my team appeared without me doing anything - what sort of group is this?)? Is it necessary to set up distribution groups or something to manage it? I realise these questions are potentially organisation-specific.
The last thing I want to do is assign roles entirely individually and then have to change it all when people join/leave/move.
If anyone could offer some insight from experience, or point me at something that explains it all in ELI5 terms I'd be really grateful.
Thanks
Hydrometric It totally depends on your data and how you wish to implement the RLS. If you have a flat role where each individual will have access to his data only then you can have only one role that will be sufficient for all. If you wish to have people to be able to access data for multiple users then you will need to create multiple roles. It is always better to keep the RLS as simple as possible. Ideally your user table should filter the data for the user based on the role he/she is assigned.
I suggest you to go through various web articles to understand how RLS work and then align it with your org requirements. below are some links to get you started.
https://docs.microsoft.com/en-us/power-bi/admin/service-admin-rls
https://radacad.com/row-level-security-configuration-in-power-bi-desktop
https://www.edureka.co/blog/row-level-security-in-power-bi/
https://blog.pragmaticworks.com/power-bi-and-data-security-row-level-security
1 Reply
- negi007
Community Champion
Hydrometric It totally depends on your data and how you wish to implement the RLS. If you have a flat role where each individual will have access to his data only then you can have only one role that will be sufficient for all. If you wish to have people to be able to access data for multiple users then you will need to create multiple roles. It is always better to keep the RLS as simple as possible. Ideally your user table should filter the data for the user based on the role he/she is assigned.
I suggest you to go through various web articles to understand how RLS work and then align it with your org requirements. below are some links to get you started.
https://docs.microsoft.com/en-us/power-bi/admin/service-admin-rls
https://radacad.com/row-level-security-configuration-in-power-bi-desktop
https://www.edureka.co/blog/row-level-security-in-power-bi/
https://blog.pragmaticworks.com/power-bi-and-data-security-row-level-security