Forum Discussion
Adding User Access Post-Lakehouse Creation
I believe I may have found a bug within our Fabric setup. I found the issue when attempting to add a new user as a viewer to a workspace. No matter the level of access (viewer, member, contributor, admin) I granted this user in the workspace, the report returned the following error:
Through some troubleshooting, I found that some existing users with the EXACT same access as my new user were able to view the report without issue. I set up a test to prove my theory; new user added, new test lakehouse, new model, point same report at new model and the user had no issues.
Has anyone had this issue before? Is there a workaround I am missing or is this a pretty large bug? Not being able to add users to access reports is a huge hit for our team.
So, the bare minimum access level to view direct lake sourced reports is: viewer to the model and readData on the underlying SQL endpoint. While testing this, I also found that you must wait until the top of every 10 minutes (12:00, 12:10, etc) for Lakehouse/SQL Endpoint access to update.
6 Replies
For reference, the report is an RDL file live connected to a semantic model that is Direct Lake storage mode.
Hi parkergeis
Thank you for reaching out microsoft fabric community forum.It looks like the issue might be related to how permissions are applied, especially with RDL reports on Direct Lake models. Even with Viewer (or higher) workspace access, the user still needs Read permissions on the semantic model itself. Also, with Direct Lake, they may need access to the underlying Lakehouse or OneLake folder.
If there's Row-Level Security (RLS) set up, double-check that the new user is mapped to a role—otherwise, they won’t see any data. It’s also worth testing in an incognito window, since RDL reports sometimes cache permission states.
The fact that it works fine with a new model/report for the same user suggests it’s more likely a config or cache issue rather than a bug. You could try redeploying the report/model as a quick test.
If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community
Thank you.Workspace viewers inherit read permissions on any semantic model in the workspace, so I don't see that being the issue. Through my troubleshooting, I did grant access to the Lakehouse (and default semantic model) and still received the same error.
Redeploying a model every time a new user needs permissions added feels unnecessary....
Hi parkergeis
We regret the inconvenience caused and acknowledges your requirements. Please consider raising a Microsoft support ticket. You can create a Microsoft support ticket using the link below:
How to create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thank you.
Hi parkergeis
May I ask if you have resolved this issue after raising support ticket? 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.
Thank you.
