Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
Check it out now!Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
i came across below methods of implementing object level security in power bi , are these right methods which I should use to implement column level security, are there any disadvantages or limitations of below methods? what is the right or appropriate way to implement object level security in power bi?
1. using field parameters
https://www.youtube.com/watch?v=ND-DYBErMwc
2. using Tableau editor
https://www.youtube.com/watch?v=G3_Gu5FTUhw
Solved! Go to Solution.
Hi @powerbiexpert22 - Object-Level Security (OLS) controls access to specific tables or columns within a dataset, ensuring users only see the objects they are allowed to access. While Row-Level Security (RLS) restricts rows of data, OLS governs access to metadata-level objects.
Use Tabular Editor to define OLS roles, as this ensures that restricted objects are inaccessible across all tools and scenarios.
Use Field Parameters when dynamic field switching is needed but security is not a concern.
Quick reference Below snapshot.
Proud to be a Super User! | |
Hi @powerbiexpert22 - Object-Level Security (OLS) controls access to specific tables or columns within a dataset, ensuring users only see the objects they are allowed to access. While Row-Level Security (RLS) restricts rows of data, OLS governs access to metadata-level objects.
Use Tabular Editor to define OLS roles, as this ensures that restricted objects are inaccessible across all tools and scenarios.
Use Field Parameters when dynamic field switching is needed but security is not a concern.
Quick reference Below snapshot.
Proud to be a Super User! | |