Forum Discussion
RLS user issue
- 7 years agoHi there
I was referring to the classic workspace in that there was a known bug even if the users had READ-ONLY access they could still see all the data.
This has only been fixed with the New App Workspace and the Viewer role.
Hi BforByron ,
If the report is stored in My Workspace, we can share the report or related dashboard with these users, they will see corresponding data based the role he/she belong to.
If the report is stored in a app workspace, as long as the users are this app workspace read-only members, they can view the report and dashboard with role filtered.
Let me know which RLS you set, Static RLS /Dynamic RLS? Did you put them into group and manage the group in DAX when seeing RLS?
Make sure you didn't give the person (who can see all the report) the accessibility to the dataset in another report, otherwise they can see all the report created based on the same dataset.
- BforByron7 years agoNew Member
Hi Dina,
The report is shared in a team workspace that all the users are members of. I am not the owner of the workspace but I do not believe these users would have any access beyond read only due to their positions. Could be possible.
This is just static RLS, I set up the roles and defined the views using the DAX input then added the users to the roles in the dataset.
This is the only report based on this dataset and all these users are new to it.- GilbertQ7 years agoSuper UserHi there
If the users are members for the Classic Workspace, even with read-only access they will still see all the data.- v-diye-msft7 years agoCommunity Support
Hi GilbertQ ,
I think you should refer to New app workspace rather than classic workspace.
For new app workspace, RLS works when the role is viewer. Anyone with Member/Contributor/Admin ignore RLS.
For classic workspace , RLS works when the role is read-only member. Anyone in the workspace with Write access will ignore RLS.
Hi BforByron ,
I would suggest you to set the report based in your own workspace, and try again. if the issue still exist, please raise your ticket to https://powerbi.microsoft.com/en-us/support/