Forum Discussion
Power BI App Allowing Share Access to Semantic Model
Hi YeahMan ,
Thank you for confirming that removing Report B, republishing the app, uploading a new copy, and re-adding it resolved the extra Share semantic model option. This reset created a new semantic model without leftover permissions.
For future updates, use a clean workspace, publish new copies of each report, and keep viewers on App-only access. Also, check the Audience › Advanced settings and Manage Permissions after each update; tenant-level or model-level “Build” restrictions can provide additional security if needed.
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.
Hi YeahMan ,
Thank you for reaching out to the Microsoft Fabric Community. Also thank you Watsky for your valuable suggestions.
Since Report A is functioning as expected within the app, and only Report B is exhibiting unexpected sharing behavior, it’s reasonable to investigate Report B’s specific setup. One possibility is that Report B might be connected to a different semantic model or dataset even if it appears similar.
We recommend going to the Power BI Service and checking the “Manage Permissions” on the dataset used by Report B to ensure that no direct or legacy access has been granted to the user. Also, double-check that Heather doesn’t have any residual access through workspace roles, even temporarily, as that can sometimes persist unexpectedly.
Additionally, if Report B was published or updated at a different time than Report A, it may be carrying different metadata or permissions especially if the app was not re-published after changes. As a next step, you might try republishing Report B and re-adding it to the app, ensuring that audience permissions are fully aligned in the app’s advanced settings.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Thanks Anonymous ,
We:
- removed reportB from the app,
- republished the app,
- downloaded the reportB,
- saved and reuploaded it with no changes,
- added reportB back in, and
- now it works.
My recommendations for using Apps are as follows:
- Create a new workspace
- Download the reports to be included
- Open/save in Desktop
- Publish to new workspace (gives you a fresh copy of the semanitic model)
- Create app for the new workspace
- Add in the reports
Other than Workspace Admins, all audience members should have App permissions only.
Hi YeahMan ,
Thank you for confirming that removing Report B, republishing the app, uploading a new copy, and re-adding it resolved the extra Share semantic model option. This reset created a new semantic model without leftover permissions.
For future updates, use a clean workspace, publish new copies of each report, and keep viewers on App-only access. Also, check the Audience › Advanced settings and Manage Permissions after each update; tenant-level or model-level “Build” restrictions can provide additional security if needed.
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.