Dynamic Hierarchy Slicer based on RLS

[SreeniBattula]

Is there a workaround to display a hierarchy slicer in Power BI that shows only the selected user and their subordinates, while excluding users higher up in the hierarchy — particularly in a Row-Level Security (RLS) scenario.

Example:
In the screenshot below, RLS has been applied for the user "Jack Bauer". The report correctly filters to show data for Jack and his subordinates. However, in the hierarchy slicer, I seee Jacks manger "Carrie Mathison", which should ideally be hidden.
I haven't found a way to dynamically limit the slicer to only the selected user and those below them in the hierarchy.

Is there any DAX logic or modeling approach that can help achieve this?

[SreeniBattula]

Thanks @TomMartens  for your response. i know about his link . but my challenge is  need to show the slicer with only selected user and his subordinates.  

[tharunkumarRTK]

@SreeniBattula 

Its a hierarchical slicer, so I guess you would have placed L1,L2,L3,L4 columns in the slicer. 

As you are aware 

Carrie Mathison name is appearing in the slicer as per the RLS filter (i.e. L2 = Jack Bauer)

Jack Bauer (L2) is the suboordinate of Carrie Mathison (L1). Applying another filter to remove/hide Carrie, will remove Jack. Because if I am not mistaken for every record where L2 is Jack, L1 would be Carrie

Need a Power BI Consultation? Hire me on Upwork

Connect on LinkedIn

Did I answer your question? Mark my post as a solution!
If I helped you, click on the Thumbs Up to give Kudos. Proud to be a Super User!

[SreeniBattula]

Filtering the data alone won’t work—we need to implement logic that builds the path and levels dynamically  based on the selected user in RLS. Unfortunately, we can't use the USERNAME() or USERPRINCIPALNAME() functions when creating custom tables.

[v-menakakota]

Hi @SreeniBattula ,

Thanks for reaching out to the Microsoft fabric community forum. 

It looks like just applying RLS won't stop higher-level users like a manager from showing up in the hierarchy slicer. This happens because the data still includes the full reporting path from top to bottom, so those names continue to appear in the slicer.

To fix this,i think you can try this the hierarchy needs to be modeled differently. Instead of using fixed levels like L1, L2, L3, you would need a structure that only includes the current user and the people who report under them. That way, the slicer will only show that part of the hierarchy and automatically exclude higher-level users like their manager.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Menaka. 
Community Support Team  

[SreeniBattula]

Hi @v-menakakota , you understood my problem, but we need a solution to create Levels L1,L2,L3... dynamically based on selected user in RLS.

[v-menakakota]

Hi  @SreeniBattula ,

Thanks for reaching out to the Microsoft fabric community forum. 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster. 

Best Regards, 
Menaka.
Community Support Team  

[SreeniBattula]

@v-menakakota , Thanks for your solution.This won;t solve the issue.

[v-menakakota · Accepted solution]

Hi @SreeniBattula  ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.

This is actually a common challenge in Power BI  getting slicers to show only the part of the hierarchy that a user is allowed to see under RLS. While there is a way to do it using dynamic hierarchy tables, it's not straightforward and does require some fairly advanced modeling.

If you haven’t already, I’d suggest sharing this on the Power BI Ideas forum. It’s definitely a feature that would make things a lot easier for scenarios like this, where we want slicers to fully respect RLS and only show relevant people in the hierarchy.
Appreciate if you could share the feedback on our Fabric Ideas - Microsoft Fabric Community  Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Best Regards, 
Menaka.
Community Support Team 

[v-menakakota]

Hi @SreeniBattula ,

Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.

If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum  we’ll be happy to assist.

Thank you for being part of the Microsoft Fabric Community.

[SreeniBattula]

Yes , Submitted this as an idea, below is the link, please vote.

Hierarchy Slicer - Microsoft Fabric Community

[v-menakakota]

Hi @SreeniBattula ,
Thanks for reaching out to the Microsoft fabric community forum. 

Fixed levels like L1, L2, L3 don't adapt dynamically based on the RLS context, which is why managers still appear in the slicer even though their data is excluded.
Please go through the below document:
Dynamic Row-Level Security (RLS) in Power BI with Organizational Hierarchy Explained - Power BI Docs

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Best Regards, 
Menaka. 
Community Support Team

[SreeniBattula]

@v-menakakota , Thanks for the solution link. i am already aware of the above given solution in the above link. it won't solve my issue. i have to hide the mangers in the the slicer.

[TomMartens]

Hey @SreeniBattula ,

you can start here: https://radacad.com/dynamic-row-level-security-with-organizational-hierarchy-power-bi

Hopefully, this will help you tackle your challenge.

Regards,

Tom