Forum Discussion
Object level security explained
- 4 years ago
v-henryk-mstf Hi Henry,
Thanks for the link, I've already read it (and many others 😅)
What I was unsure of - and couldn't seem to decipher from the blog posts - was whether someone not in any of the security roles could see the objects as a default. But I tested this yesterday, and found that if it's not specified whether an employee should see or not see the objects by OLS, then they can't access the report at all (it throws an error saying something like RLS is blocking access). If I put the employee in the "cannot see" OLS role, he could see only the visuals from un-secured objects in the report. And lastly, he could see everything when allocated the "can see" OLS role.So, some good-old fashion testing answered my question. I will close this post.
Thanks
Hi rebeccaETE ,
See if the following blog links are helpful to you.
If the problem is still not resolved, please point it out. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- rebeccaETE4 years agoHelper I
v-henryk-mstf Hi Henry,
Thanks for the link, I've already read it (and many others 😅)
What I was unsure of - and couldn't seem to decipher from the blog posts - was whether someone not in any of the security roles could see the objects as a default. But I tested this yesterday, and found that if it's not specified whether an employee should see or not see the objects by OLS, then they can't access the report at all (it throws an error saying something like RLS is blocking access). If I put the employee in the "cannot see" OLS role, he could see only the visuals from un-secured objects in the report. And lastly, he could see everything when allocated the "can see" OLS role.So, some good-old fashion testing answered my question. I will close this post.
Thanks