-
Bharti Goel
- December 26, 2022
Ever wondered how to ensure data security down to the smallest detail? What if you could control access not just at the database level but right down to individual data points? Enter Object Level Security: the key to granular control over your data. But how does it work, and why is it crucial in today’s data-driven world?
What is Object Level Security, and what does it do
There are different types Of Data Security In Power BI. One of them is Object Level Security.
Simply put, OLS in Power BI allows model authors to protect specific columns or tables from report viewers. It helps maintain privacy. Let’s consider an example where a table or a column contains some private information. In this case, the table or the column can be restricted. Therefore, only certain viewers have a view of it and can interact with it. Additionally, restricting object names and metadata is also possible.
The object-level security is an additional layer of security. It is added to prevent inappropriate users from accessing business-critical or sensitive personal data. Also, the secure tables or columns are not visible to users who do not have appropriate access to them.
In short words, object-level security secures and hides sensitive and personal data from being discovered.
How to Set up Object Level Security (Step-by-step)
There are certain steps that one needs to follow for setting up object-level security. You can’t specify OLS directly from Power BI Desktop. Instead, you’ll need an external tool called Tabular Editor.
9 steps for configuring object-level security
Step 1: Create a Model that contains all of your Object Level Security Rules
In the Power BI Desktop, just create a model that contains all of your OLS rules. Further, follow the steps listed below to define the security roles.
1.1 Either configure a DirectQuery connection or import the data into your Power BI desktop report.
1.2 Now, select Manage Roles from the Modeling tab.
1.3 Now, select Create from the Manage Roles window.
1.4 Under roles, provide a name for the role created.
1.5 Select the table on which you wish to apply the DAX rule under the Tables section.
1.6 In the Table filter DAX expression box, enter the DAX expression.
1.7 To validate the DAX expression that you created, select the checkmark above the expression.
1.8 Now select Save, and you are all done.
Step 2: Select the Tabular Editor on the External Tools ribbon.
You select the tabular editor of the external tools ribbon. In case the Tabular Editor button is not visible, prefer installing the “program.” The Tabular Editor will automatically connect to your model once the “program” is installed and opened.
Step 3: Click Model View
Click on the Model view now. You will then find a drop-down menu under “Roles.” Select that, and all the roles created in the previous step will appear over there.
Step 4: Role Selection
Select the role for which you want to enable the object-level security definition. Further, expand the Table permissions.
Step 5: Select either “None” or “Read” permission for the column or the table.
- None: By selecting “None,” the OLS will be enforced. Also, the column or the table will be hidden from that role.
- Read: By selecting “Read,” the column or the table will be visible to that role.
Step 6: Save the changes
You need to save your changes after defining the OLS roles.
Step 7: Publish the dataset
Publish your dataset to the Power BI Service from the Power BI Desktop.
Step 8: Assign Members or Groups
Navigate to the Security page in the Power BI Service. Assign members or groups to their appropriate roles.
Step 9: Save
Do not forget to hit the Save button.
On completing these nine steps, we will be able to define the OLS rules. A notification that “field can’t be found” will appear to the users without appropriate permissions.
Difference between Row Level Security (RLS) & Object Level Security (OLS)
| Basis | Row-level Security | Object-level Security |
| Definition | We can use Row-level security (RLS) to restrict data access at the row level for given users. | We can use Object-level security (OLS) to restrict data access for sensitive tables or columns from report viewers. |
| License | Available in all licenses | Available in Pro & Premium (paid) Licenses |
| Available Since | Since starting (2015) | Feb 2021 |
| How it works | With RLS, the Metadata of the objects can be viewed. | With OLS, the Metadata of the objects cannot be viewed. It feels like totally deleted. |
| Pre-requisites | RLS can be configured from Power BI Desktop itself. | OLS Configuration is possible with the help of the external tool, Tabular Editor (licensed software). |
| Direction of Security | The direction of the rule applied is horizontal. | The direction of the rule applied is vertical. |
| Limitation | In the Power BI service, members of a workspace have access to datasets in the workspace. RLS doesn’t restrict this data access. | It only applies to “Viewers” in the workplace. It does not apply to members assigned as Admin, Member, or Contributors, as they have edit permissions for the dataset. |
| Dynamic | RLS is static & Dynamic. | Microsoft has no Dynamic OLS, it’s only static. |
This was all about OLS. We hope you enjoyed reading this blog. Your thoughts are welcome in the comments section.
Curious about what lies ahead for Power BI? With groundbreaking strides in AI, IoT, AR/VR, and data security, Power BI is set to not only elevate our data visualization and interpretation but also transform the very way we engage with data. You should certainly learn Power BI to stay ahead in your career. You can also explore General Q&A about Power BI for your career.
FAQ – Object Level Security in Power BI
Q1. Who in my team should be responsible for setting up Object Level Security (OLS)?
Typically, BI developers or data modelers handle OLS because it requires understanding of DAX, Tabular Editor, and dataset structures. Team leads or managers can review the roles and permissions to ensure proper governance.
Q2. Can business users or report consumers request changes to Object Level Security (OLS) rules?
Yes, they can request changes, but only admins or model owners can implement them. OLS ensures sensitive columns and tables are hidden from unauthorized users, so changes should follow corporate data security policies.
Q3. How can corporate teams ensure Object Level Security doesn’t block necessary collaboration?
Teams should define roles carefully and test permissions in the Power BI Service before publishing. Only restrict sensitive columns or tables, and make sure collaborators with Admin or Member roles retain necessary access.
Q4. How does Object Level Security (OLS) impact HR, finance, or sales teams handling sensitive data?
OLS allows these teams to hide confidential info like salaries, bonuses, or personal employee details while still enabling analysis on other data. This ensures compliance with privacy regulations and internal policies.
Q5. Are there corporate training programs to teach Object Level Security (OLS) setup and management?
Yes, Edu4Sure provides corporate training for teams, covering OLS, RLS, Tabular Editor, and best practices. Training helps BI teams implement security properly, maintain compliance, and manage sensitive datasets efficiently.
Do you need professional training, or would you like to discuss your needs with our trainers? You can contact us via partner@edu4sure.com or WhatsApp at +91-9555115533.
