Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Aprildog
Regular Visitor

Users with Same Permissions Seeing Different Data

Hi all, 


I have a report which I share via a workspace controlled by Row Level Security. I have a permission set with 5 users in giving them full access to a particular departments information, this information contains financial data, income, pay costs and non-pay costs. One member of that group, on logging in, can only see pay costs, they can't see income or non-pay, everyone else can see everything. I've tried clearing the cache, I've tried removing their access and re granting it. I've assigned them to a different group and got the same results, pay costs only. There don't appear to be any filters saved at their end. 

I'm at a loss with what to do now, when I do "view as" it all looks as expected. 

Any help would be appreciated! 

Thanks in advance

1 ACCEPTED SOLUTION
v-lgarikapat
Community Support
Community Support

Hi  @Aprildog ,

Thanks for reaching out to the Microsoft fabric community forum.

@BhavinVyas3003 ,

@powerbidev123 Thanks for your prompt response

 @Aprildog  in addion to @BhavinVyas3003 , @powerbidev123  

@Aprildog  Could you try the troubleshooting steps below?

 

Since your View as shows the correct data and others with the same permission set have full visibility, this likely points to a user specific issue rather than a flaw in your RLS setup. First, double check that the user has Viewer access in the workspace, because RLS only applies to Viewers higher roles like Contributor or Admin bypass RLS entirely and can create odd visibility quirks. If your RLS rules use USERNAME() or USERPRINCIPALNAME(), confirm that the user's email or login format matches exactly what the DAX is filtering against, as mismatches can silently cause access failures. Inspect your relationships in the model, too if Pay Costs is exposed while Income and Non-Pay are missing, it may be due to one-way filters that don’t propagate RLS across all tables, so enabling bi-directional filtering might help. You said you cleared cache, but it’s worth having the user test in incognito mode or on another browser/device, or even the Power BI mobile app, just to rule out local quirks. Also confirm that there aren't any visual-level filters, bookmarks, or personalized views that are subtly limiting visibility for that user. A good diagnostic move is to assign them temporarily to a simple role with a TRUE() filter if they see everything then, the issue likely lies in how your dynamic logic is matching their identity.

Solved: RLS issue: how to enable some users to see all row... - Microsoft Fabric Community

Solved: Re: Row level security security issues - Microsoft Fabric Community

 

We appreciate your engagement and thank you for being an active part of the community.

If you're still facing challenges, feel free to let us know we’ll be glad to assist you further.

Looking forward to your response.

Best regards,
LakshmiNarayana.

View solution in original post

6 REPLIES 6
v-lgarikapat
Community Support
Community Support

Hi  @Aprildog ,

Thanks for reaching out to the Microsoft fabric community forum.

@BhavinVyas3003 ,

@powerbidev123 Thanks for your prompt response

 @Aprildog  in addion to @BhavinVyas3003 , @powerbidev123  

@Aprildog  Could you try the troubleshooting steps below?

 

Since your View as shows the correct data and others with the same permission set have full visibility, this likely points to a user specific issue rather than a flaw in your RLS setup. First, double check that the user has Viewer access in the workspace, because RLS only applies to Viewers higher roles like Contributor or Admin bypass RLS entirely and can create odd visibility quirks. If your RLS rules use USERNAME() or USERPRINCIPALNAME(), confirm that the user's email or login format matches exactly what the DAX is filtering against, as mismatches can silently cause access failures. Inspect your relationships in the model, too if Pay Costs is exposed while Income and Non-Pay are missing, it may be due to one-way filters that don’t propagate RLS across all tables, so enabling bi-directional filtering might help. You said you cleared cache, but it’s worth having the user test in incognito mode or on another browser/device, or even the Power BI mobile app, just to rule out local quirks. Also confirm that there aren't any visual-level filters, bookmarks, or personalized views that are subtly limiting visibility for that user. A good diagnostic move is to assign them temporarily to a simple role with a TRUE() filter if they see everything then, the issue likely lies in how your dynamic logic is matching their identity.

Solved: RLS issue: how to enable some users to see all row... - Microsoft Fabric Community

Solved: Re: Row level security security issues - Microsoft Fabric Community

 

We appreciate your engagement and thank you for being an active part of the community.

If you're still facing challenges, feel free to let us know we’ll be glad to assist you further.

Looking forward to your response.

Best regards,
LakshmiNarayana.

Hi @Aprildog ,

I wanted to follow up and confirm whether you’ve had the opportunity to review the information we provided. If you have any questions or need further clarification, please don’t hesitate to reach out.

 

We truly appreciate your continued engagement and thank you for being an active and valued member of the community.

 

We look forward to hearing from you.

Best regards,
Lakshmi

Hi @Aprildog ,

I just wanted to check if your issue has been resolved. If you still have any questions or need help, feel free to reach out I’m happy to assist.

Thank you for being an active part of the community. Looking forward to hearing from you!

Best regards,
Lakshmi

Hi all, 

Apologies for the delay in coming back! It took me a little bit to work through the options to find what worked! It turned out that although we had cleared the cache it had saved some drill through filters to each of the pages which weren't clearing or visible. 

The reset to default worked on clearing all them so thank you very much!!

BhavinVyas3003
Super User
Super User

Ask the user to clear personal bookmarks and disable persistent filters in the report settings. Also, test using a different browser or incognito mode. If the issue persists, recheck RLS logic and DAX measures that may filter out income/non-pay data specifically for that user.


Thanks,
Bhavin
Problem solved? Hit “Accept as Solution” and high-five me with a Kudos! Others will thank you later!
powerbidev123
Solution Sage
Solution Sage

Hi @Aprildog 

1. Check if Personalized Visuals or Persistent Filters Are On

Power BI remembers filters for users per report (called "persistent filters").

 

Ask the user to:

 

Open the report

 

Click "Reset to default" in the top-right corner of the report (⚠️ not just clear filters, but reset entire view)

 

🔁 Then refresh the report.

 

🔹 If "Reset to default" fixes it, they had a saved state (visual filters, slicers, bookmarks, etc.).

 

2. Check for Personalized Visuals (New Feature)

If you’ve enabled “Personalize Visuals”, the user might have customized the visual and removed or filtered out income/non-pay categories.

 

➡️ Ask them to click the ellipsis (•••) on the affected visual and select "Reset to default" or "Revert changes".

 

3. Validate RLS from Service (Not Desktop)

Use "Test as role" in Power BI Service, not just in Desktop:

 

Go to:

 

Dataset → Security

 

Select their group or username

 

Click “Test as role”

 

Open the report and verify what’s shown.

 

Sometimes “View As” in Desktop behaves slightly differently, especially if any service-level filter is cached.

 

4. Check the Underlying Data

There’s a chance the data row-level logic (e.g., DAX filter expressions) is allowing them to see only a subset due to unintended logic.

 

Review your RLS rule logic (DAX), especially if it references:

 

RELATED(UserPermissions[UserEmail])

Make sure:

 

The user’s email (from USERPRINCIPALNAME() or similar) matches exactly

 

The logic does not accidentally filter based on department/category (pay cost vs income)

 

5. Test in a Separate Report

As a sanity check:

 

Create a new report from the same dataset

 

Share with the user (use the same RLS config)

 

See if they now see all categories

 

If they do — then it’s something specific to the original report’s state, not RLS or data model.

 

 

 

 

 

 

 

 

 

 

 

 

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.