Should I create two datasets to separate what teams can see?

[bdv99]

Hello everyone, newish user here, really appreciating the tips I'm finding in this community. Thank you.

I would love to get some advice on how to best implement this scenario: there are two distinct teams in my business that need power bi data.  One is the finance team, they needing general ledger, debtor/creditor etc. The other is the product team, who need category/subcategory/style/colour amongst many other things.

Both will want to report revenue, product margin, inventory levels, volumes, budget. Those measures need to be identical no matter which way you slice the data. Obviously within one data model you're pretty safe in terms of ensuring all measures and dimensions are operating correctly, however I need to segregate true company profitability - finance data - from selected users.

Product Team - product measures

Finance Team - all

Am I better to just run another data model for Finance, which includes everything in the Product version plus all the GL stuff ? This guarantees access level security, but feels like a whole heap of duplication if we need to make changes/include new dimensions or measures etc. I can't see a way to segregate certain data elements in PBI.

Really appreciate your time,

[Dhairya · Accepted solution]

You can use Row Level Security (RLS) for hide/show rows based on Roles assigned based on values of record.
If you want to hide/show Columns of table or whole table you can implement Object Level Security (OLS) for that you will need tabular editior as external tool.

For RLS you can refer : https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-rls

For OLS you can refer : https://towardsdatascience.com/the-ultimate-guide-to-row-level-and-object-level-security-in-power-bi....

For downloading tabular editor free version: https://github.com/TabularEditor/TabularEditor

[olgad]

There is also a Row Level Security based on Roles and rows, if you wanna hide certain rows of info, also Object Level Security that can be set up in External Editor, to hide columns or tables from particular user roles.