Forum Discussion
Row Level Security Clarification
I hope someone can help provide some clarification on row level security. I have a dashboard that filters data based on four different facilities. I was asked that two individuals only see data for two of the facilities. I created the two facilities under manage roles. I published the dashboard to the workspace and added their e-mails under each facility in row level security settings. My thinking when I did this is that only the two e-mails would be impacted. It turns out that other people who view this dashboard and have access to all the data are getting the below message. To get around this had to add all facilities to manage roles and add their e-mails to each facility in row level security settings. Does this sound right to anyone? I would have thought that anyone not added to row level security would have access to all data within the dashboard. Thanks for your help.
Welcome to the wonderful world of RLS 🙂
Just to clarify
Power BI RLS operates as a restrictive model.
When you define roles and rules within a Power BI dataset and publish it with RLS enabled, the system assumes that all data access should be controlled by these roles.
Here's the key takeaway:
- If RLS is defined for a dataset, users who are not explicitly assigned to any role will be restricted from seeing any data. Power BI doesn't automatically grant access to all data if a user isn't part of a specific RLS role.
So indeed to fix this issue you have to create a role which has access to everything
1 Reply
Welcome to the wonderful world of RLS 🙂
Just to clarify
Power BI RLS operates as a restrictive model.
When you define roles and rules within a Power BI dataset and publish it with RLS enabled, the system assumes that all data access should be controlled by these roles.
Here's the key takeaway:
- If RLS is defined for a dataset, users who are not explicitly assigned to any role will be restricted from seeing any data. Power BI doesn't automatically grant access to all data if a user isn't part of a specific RLS role.
So indeed to fix this issue you have to create a role which has access to everything