Forum Discussion
Link Sharing with Row Level Security
- 4 years ago
Just checking back in with the solution on this.
It turns out that we believe the users who reported the issue were actually seeing what they were supposed to see and just didn't realize it.
The reason the issue persisted in our internal testing is because we were removing people from the workspace just before assigning RLS and testing. We met with our Microsoft reps on this and it turns out that you need to wait at least 1 hour after removing someone from a workspace before assigning RLS. This has to do with a permissions job that runs hourly.
Thanks everyone for your help.
HI porterm3
This sometimes happens if the report is cached.
What I typically do is to share reports via an App. Because the user clicks on the app link it will then first see their RLS permissions and then show them the valid data.