March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi,
I'm creating a summary report that uses several semantic models from different workspaces, using Direct Query. The issue is that most users cannot see visuals that are not part of the workspace they belong to and I'm trying to figure out what permissions are missing. An import detail is that my summary report should be visible for all users in my company but the different semantic models and corresponding existing reports/dashboards of each team on specific workspaces are restricted to each team only.
Would it be enough to provide access to different semantic models? If so, how can I provide access to all users at once and not one by one? Is through sharing link? And if user access is provided only on semantic model level (not in the different workspaces neither reports), does this mean that users would be only to see the data displayed in my summary report and not the whole data, right?
Thank you very much for you support.
Solved! Go to Solution.
The solution was to provide user access to the semantic models using the option Direct Access and unticking all the checkboxes, ensuring only read access (no build, reshare, etc). I had to use an AD Group to ensure access to all users in my organization. Additionally, using the option OneLake, I asked some users to check if they could see the semantic models for which access was given and the option "Explore data" was deactivated, meaning they can only see the data I display in my report and nothing else (given that some details are confidential). I didn't had to provide any permission in the different workspaces, so the users cannot access any team specific workspaces or reports.
The solution was to provide user access to the semantic models using the option Direct Access and unticking all the checkboxes, ensuring only read access (no build, reshare, etc). I had to use an AD Group to ensure access to all users in my organization. Additionally, using the option OneLake, I asked some users to check if they could see the semantic models for which access was given and the option "Explore data" was deactivated, meaning they can only see the data I display in my report and nothing else (given that some details are confidential). I didn't had to provide any permission in the different workspaces, so the users cannot access any team specific workspaces or reports.
Glad that this works for you. Personally I think that not giving Build access is counterproductive.
uses several semantic models from different workspaces
All report users must have access to all workspaces. If you share via app them all users must have "installed" (registered) all apps from the participating workspaces.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |