Forum Discussion
Helper IPower Block Drill Down
Can I block the drilldown for a specific user in Power BI? I only have one view that has the cost center and when I drill down it goes down to the person level. Can I configure the RLS so that certain users cannot go down to the employee level or, if not, not see the employee information when they go down the level? This is taking into account the same view... Or would the best way be to create a separate view?
Hi PedroModa,
Thanks for reaching out to the Microsoft fabric community forum.
This is a common scenario when you want to maintain a unified report view but restrict access to sensitive information. To clarify, PowerBI does not allow conditional control of the drilldown feature itself meaning, you can't block the act of drilling down based on who the user is. However, you can absolutely use Row-Level Security (RLS) to ensure that certain users cannot see employee-level data, even if they drill down.
You can handle it by:
* Applying RLS on the employee table. Create a security role that filters out employee-level rows for users who shouldn't see them. For example, you could filter by a column like [IsRestrictedUser] or apply a rule that limits access to only certain cost centers or hides employee data entirely.
* The Impact of RLS on Drilldown. When a user with restricted access drills down in the visual, the employee-level data will either be completely blank (no rows visible), or shows only the subset of employee data allowed by the RLS rule.
* No need to create a separate view unless you want different layouts or visuals. With RLS applied, you can keep the same report structure and let Power BI handle the data filtering based on the user identity.
I would also take a moment to thank danextian and Daniel29195, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
6 Replies
- Daniel29195
Community Champion
Hello , did you check the dynamic RLS ?
Here's the article for reference: Dynamic Row Level Security with Power BI Made Simple – RADACAD.
Let me know if this approach works for your case. If not, feel free to reply to this comment—I’d be happy to walk you through it step by step.
Best,
Daniel - danextian
Super User
Hi PedroModa
RLS restricts access to the rows. If the a user drills down and RLS has been setup, the user will still be able to drill down into the employee level but will only see his own records. If you want to disable drilldown only for specific users you can add a condition to a measure so it shows blank when those conditions are met.
IF ( ISINSCOPE ( 'table'[employee level] ) && USERPRINCIPALNAME () IN VALUES ( 'restrictiontable'[list of employees to restrict] ), BLANK (), [the measure] ) Hi PedroModa,
Thanks for reaching out to the Microsoft fabric community forum.
This is a common scenario when you want to maintain a unified report view but restrict access to sensitive information. To clarify, PowerBI does not allow conditional control of the drilldown feature itself meaning, you can't block the act of drilling down based on who the user is. However, you can absolutely use Row-Level Security (RLS) to ensure that certain users cannot see employee-level data, even if they drill down.
You can handle it by:
* Applying RLS on the employee table. Create a security role that filters out employee-level rows for users who shouldn't see them. For example, you could filter by a column like [IsRestrictedUser] or apply a rule that limits access to only certain cost centers or hides employee data entirely.
* The Impact of RLS on Drilldown. When a user with restricted access drills down in the visual, the employee-level data will either be completely blank (no rows visible), or shows only the subset of employee data allowed by the RLS rule.
* No need to create a separate view unless you want different layouts or visuals. With RLS applied, you can keep the same report structure and let Power BI handle the data filtering based on the user identity.
I would also take a moment to thank danextian and Daniel29195, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamHi PedroModa,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. And if you're still looking for guidance, feel free to give us an update, we’re here for you.
Best Regards,
Hammad.
Hi PedroModa,
Hope everything’s going smoothly on your end. As we haven’t heard back from you, so I wanted to check if the issue got sorted.
Still stuck? No worries just drop us a message and we can jump back in on the issue.Best Regards,
Hammad.
