This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
I have a semantic model in Power BI where I have two data tables: Sales and P/L. I also have two dimension tables: Market and User.
The Market dimension table is mapped to both Sales and P/L data tables.
I need to set up dynamic row level security where user access should be based on the following:
P/L: User will only see data for the market they are responsible for.
Sales: Users will see sales for all the markets except one.
What's the best way to implement this? Any help would be highly appreciated!
Solved! Go to Solution.
Hi @Hazzzy,
Thank you for reaching out to the Microsoft Fabric Community!
Based on your requirements, you can achieve Dynamic Row-Level Security (RLS) by defining two different security rules within Power BI:
Suggested Approach:
Ensure that your User table contains information about the markets each user has access to (e.g., ResponsibleMarket and ExcludedMarket).
Implement Dynamic RLS filters using DAX within the Power BI Manage Roles feature:
Since the Market dimension is linked to both Sales and P/L tables, the RLS filters applied on MarketID should propagate to the fact tables accordingly.
Please Accept as solution if this meets your needs and a Kudos would be appreciated.
Thank you.
Hi @Hazzzy,
Thank you for reaching out to the Microsoft Fabric Community!
Based on your requirements, you can achieve Dynamic Row-Level Security (RLS) by defining two different security rules within Power BI:
Suggested Approach:
Ensure that your User table contains information about the markets each user has access to (e.g., ResponsibleMarket and ExcludedMarket).
Implement Dynamic RLS filters using DAX within the Power BI Manage Roles feature:
Since the Market dimension is linked to both Sales and P/L tables, the RLS filters applied on MarketID should propagate to the fact tables accordingly.
Please Accept as solution if this meets your needs and a Kudos would be appreciated.
Thank you.
Hi @Hazzzy,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thank you.
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 27 | |
| 25 | |
| 25 | |
| 21 | |
| 14 |
| User | Count |
|---|---|
| 50 | |
| 44 | |
| 20 | |
| 18 | |
| 18 |