You have a Power BI dataset that contains two tables named Table1 and Table2. The dataset is used by one report. You need to prevent project managers from accessing the data in two columns in Table1…

Question

Explanation

This question tests your knowledge of Object-Level Security (OLS) in Power BI, which allows administrators to restrict access to specific columns or tables for certain roles. The goal is to hide the Budget and Forecast columns in Table1 from project managers without affecting other users.

Approach. The correct sequence involves: (1) Open the .pbix file or live-connect dataset in Tabular Editor (a third-party tool required for OLS configuration, since Power BI Desktop's native Manage Roles UI does not expose column-level OLS). (2) In Tabular Editor, create a new role (e.g., 'Project Managers'). (3) For that role, set the Object-Level Security permission on the Budget and Forecast columns in Table1 to 'None' (which hides them entirely from that role). (4) Publish the dataset to the Power BI Service and assign the project manager users or security group as members of the 'Project Managers' role under the dataset's Row-Level Security settings. This sequence is required because OLS is a Tabular model feature not exposed in the Power BI Desktop UI - Tabular Editor is the standard tool to configure it, and role membership is managed post-publish in the Service.

Concept tested. Object-Level Security (OLS) in Power BI - specifically, how to restrict access to individual columns using Tabular Editor to define roles with column-level 'None' permissions, and then assigning users to those roles in the Power BI Service.

Reference. Microsoft Learn: Object-level security (OLS) in Power BI - https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-ols

No community discussion yet for this question.