Forum Discussion

rebeccaETE's avatar
rebeccaETE
Helper I
4 years ago
Solved

Object level security explained

Hi all,    I'm looking into using Object Level Security (OLS) for a table in my data model but I can't wrap my head around the security roles. In all the videos I've seen on how to set-up OLS, they...
Need Help
  • rebeccaETE's avatar
    rebeccaETE
    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 

rebeccaETE's avatar
rebeccaETE
Helper I
4 years ago

amitchandak Yes, the thing is that I do want to restrict access to the content, and as I can gather with: 

 

Masking: "Sometimes, you want to show all the information to all the users, but you want to hide the sensitive data"- I don't want to show all the information to all the users. I want them to see nothing at all, if they don't have the right access level. 

 

and 

 

Sensitivity labels: "In the Power BI service, sensitivity labeling does not affect access to content. " - I do want to affect access.