Forum Discussion
Object Level Security "Reverse" Role
Hi JustDavid
If you have applied built-in restrictions on certain columns, non-HR users won’t be able to access them directly, which can sometimes cause errors in matrix visuals. To avoid this, you can either:
-
Remove the restricted columns from the matrix entirely for non-HR users.
-
Use role-based logic to conditionally display blank (e.g : Restricted) in those columns for unauthorized users.
Reference : Object-Level Security (OLS) with Power BI - Microsoft Fabric | Microsoft Learn
Hope this helps,
Thank You.-
Hello Davis !
I am glad to help, we all learning here 🙂
With OLS, hidden columns don’t just disappear from the fields pane they’re not addressable at all so any visual or measure that use them will fail for users in the deny role.
OLS is allow by default which means to deny columns to everyone except HR, you must assign a deny role to everyone.
You need an AAD group that includes everyone who uses the report and add it under the dataset security tab and map it to your all employees role.
If you need more help please tell me.
So if I understand you correctly, I have to list all employees except Mary, Jane and John to the 'All Amployee'?
If I were to do that, would these employees be able to see the matrix table that I created, with an exception of the columns that I have hindered them from vieweing?
Exactly ! non HR users will see the visual as long as the matrix don’t reference the hidden columns and if the matrix uses employee name or salary or any measure that reads them you will have that error because the all employees role since OLS makes those columns non addressable.
Is there a way then for non HR users to be able to see the matrix table that I've created with the restricted columns "built-in", in a sense they are not able to see the "columns" without giving that error?
Hi JustDavid
If you have applied built-in restrictions on certain columns, non-HR users won’t be able to access them directly, which can sometimes cause errors in matrix visuals. To avoid this, you can either:
-
Remove the restricted columns from the matrix entirely for non-HR users.
-
Use role-based logic to conditionally display blank (e.g : Restricted) in those columns for unauthorized users.
Reference : Object-Level Security (OLS) with Power BI - Microsoft Fabric | Microsoft Learn
Hope this helps,
Thank You.-