RLS issue for a specific user? Previously had member access to workspace

[AMARSHALL80]

Hi there,

I've been setting up reports using principalname functionality and it's great.  Have published my report to 2 different workspaces to test and 99% of the time it works perfectly.  Where i'm stuck is where a user previously had member access to a workspace - when i update to viewer, the RLS still doesnt seem to work.

On my 2 test workspaces, it's just the user who previously had elevated access on each that it doesnt work for?

is there something i'm missing about remove/reducing access to a workspace to ensure RLS works?

Thanks in advance.

[Burningsuit]

Hi @AMARSHALL80 

It sounds like the "Viewer" user still has "Build" rights on the Dataset.

To check this, in the Workspace, on the Dataset you have implemented RLS, on the three dots (more options) select "Manage Permissions", look at "Direct Access" and you'll see the list of users with access and their levels. I expect that your users has "Viewer" and "Build", to remove Build, use the three dots on the right of the list and select "Remove Build".

Hope this helps

Stuart

[AMARSHALL80]

hi there,

Just to let you know by adding content to a new workspace it's solved my issue.  So it's just about finding out what access with a workspace is stopping the RLS from working for the user.  have checked the dataset and report permissions, so wondered if it could be access to other non related datasets or reports in the workspace?  

[AMARSHALL80]

Thanks for responding - appreciate that!  I had removed the user that i had an issue with from the dataset access - so they are just showing as part of an active directory group now (as per the other users) with  Read access only.  Do you know if my cache could be causing  the issues in relation to RLS?  i'm clutching as straws here, but i just can't see anywhere on report or dashboard where the affected user has any permissions (now) different to all the other users in the active directory group, for whom the RLS works perfectly.