Forum Discussion
Users with Same Permissions Seeing Different Data
Hi Aprildog ,
Thanks for reaching out to the Microsoft fabric community forum.
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
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.