Forum Discussion
Permissions for report using several semantic models
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.
