RLS issues

[SeniorJunior]

Hi all, 

I have an exising report that has recently moved workspaces and adding new people to the RLS doesn't seem to be working for them. 

I have a spreadsheet with their name, email and permission level set out and that has been updated, the three dots and Security tab has also been updated, but there are still issues and they are being told that they don't have permissions to view the data set. 

They are not workspace members (but they do have access to the app that the report is published into and show up in the permissions as such).

What am I missing?

Thanks for any pointers! 

[Joe_Barry]

Hi @SeniorJunior 

What is the licensing situation at your company? Premium or each reader has a Pro Licence? If it's premium, it could be the report isn't in a Premium Workspace or if it's Pro Licences, maybe the users need a licence?

When you mention permission, do you mean that they can see the report, but RLS is preventing them from viewing it?

You never mentioned anything about how your RLS is set up. In the report how are the roles created? Is the spreadsheet built into the report also? How is the Relationship setup between the Spreadsheet and the Fact table you are filtering? Maybe there is some spaces at the end of the email address in the spreadsheet?

Can you provide some more information on this? Maybe I can help further

Joe

[SeniorJunior]

@Joe_Barry  Thanks for you response.

So, the roles are set up in an Excel file which is then linked into the report similar to this: Dynamic Row Level Security with Power BI Made Simple - RADACAD with the table filtering, DAX, etc all very similar and had been working fine until recently for these new users.  

I manage the Excel, so know that there's no spaces at the end of the columns, drop down list for roles so there can be no typos. 

Company is a PPU with everyone on it. 

They can see the report but get a message that permissions are denied as they don't have access to the underlying dataset (that uses RLS).

[Joe_Barry]

Good morning @SeniorJunior 

It seems that you have everything correct. How is the relationship built between the Spreadsheet and the FACT Table? Email to Email?

If it's possible can you send me a screenshot of the relationships with a clear view of what columns are being used. Also a screnshot of the Roles under the Modeling tab and the DAX formula for that?

Thanks

[SeniorJunior · Accepted solution]

Thanks for your offer of help. I re-checked everything yesterday, double checked all the various things we've discussed and then opted to republish the report (same name, etc) and update the app again. 

For some reason it is now working, which is great news, as I was running out of options! 

Sadly this won't be much help for anyone else finding this thread on the search feature, but hopefully between the two responses I've had there's a good checklist for people to work through. 

Thanks again for your kind assistance. 

[Joe_Barry]

The main thing, is that the issue is resolved for you.

All the best

Joe

[grazitti_sapna]

Hi @SeniorJunior,
It sounds like you’ve taken most of the necessary steps, but there are a few areas that could be causing the permissions issue. Here’s a checklist to ensure everything is correctly configured:

1. Verify RLS Role Assignment: Ensure that the users are correctly added to the relevant roles in the Row-Level Security (RLS) setup. Double-check if they have been assigned the proper roles in the Power BI Service:

   • Go to the Data Set in the Power BI Service.
   • Click the three dots (...) next to the data set, select Security, and make sure the users are explicitly added to the roles here.

2. Review App Permissions: Since users have access to the app, ensure the app permissions have been published or updated recently:

   • Go to the App Workspace, update the app, and republish it to reflect any new permissions or RLS settings.

3. Confirm Data Set Permissions: Make sure the data set is shared properly:

   • Users must have the correct permissions for the underlying data set, even if they have access to the report. In the Power BI Service, under Manage Permissions for the data set, verify that these permissions are configured properly.

4. Check Licensing: Users must have the appropriate Power BI licenses (either Pro or access to a Premium capacity workspace). If the report is in a Premium workspace, ensure that non-Pro users are covered.

5. Workspace Settings: Although the users are not workspace members, review the workspace settings to ensure there aren't restrictions on access to the data set for non-members.

6. Refresh RLS Assignments: Sometimes, there can be a delay or issue with syncing RLS settings. You may want to try removing a user from the role, saving it, and then adding them back to force a refresh.

7. Check Data Privacy Settings: If your data set is connected to external data sources, data privacy settings might restrict access. Verify that these settings aren't causing the issue.

8. Clear Cache and Sign Out/In: Ask affected users to clear their browser cache, sign out of Power BI, and sign back in to ensure there isn’t a caching issue on their end.
   

If I have resolved your question, please consider marking my post as a solution🎉. Thank you!

[SeniorJunior]

Thank you - a very useful check list, sadly, I have done all of these steps already:

1. This is managed by an Excel that the Power BI links to, this link is still active and the logic works. 
2. The users have permissions in the app to view the report, and the app has been updated. 
3. The users appear under Manage Permissions with 'App' next to their name
4. Licensing is not an issue. 
5. Could you expand on this one a bit more? I don't see why it would have happened, but just in case...
6. Already tried! 
7. All internally managed data.
8. This is on my list of last options, also asking that they try another browser.