RLS doesn't update with changes in workspace access

[PC20]

I created a new workspace and provided Viewer access to a UserA. 

Created a Dynamic Role in Power BI and published to this workspace.

RLS works as expected, filtering data.

I changed the UserA access to Member. But, RLS is still applied. Whereas, as per documentation UserA should be able to see the whole data.

I have tried refreshing the reports, dataset, using Incognito modes, deleteing and publishing report and datasets.

But RLS doesn't affect with changes in access to a workspace.

The only thing that works is if I delete & create the workspace again.

[v-yangliu-msft]

Hi  @PC20 ,

I would like to confirm with you that you are using the view as role feature of RLS to test the data that this user's RLS can see?

If so, according to my testing and research on the view as role feature of RLS, I believe that the problem you are experiencing is a backend logic of the "Test as role" feature.

The most common problem when administrators simulate other users is that the simulated user's permissions are out of date. power BI maintains a cache of valid user permissions, which are kept up to date by background jobs. Permission refresh jobs are typically scheduled once an hour for each user. However, if a user has not been active in Power BI for a period of time (or if they have never used Power BI), such jobs will hang until the user logs in again (to reduce the load on the system). This can cause the simulation function to use outdated permissions and display a view of the data that does not match the view of the data seen when the simulated user logs in."

This is a background operation of Power BI to optimize the maintenance of user rights cache to consume server resources, and only through the "test as role" simulation test process, will not actually cause data leakage, after the user login data in theory will be normal according to the configuration of the corresponding data display.

Best Regards,

Liu Yang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[PC20]

Thank you @v-yangliu-msft . This makes sense. I was wondering that this could be a cache issue, but was unable to figure out the details.
Is there any documentation regarding these Refresh Jobs? And any workaround to avoid this?
Re-creating a workspace and re-publishing seems tedious and unnecessary.