Forum Discussion
Org App doesn't grant semantic model access although report and model are in the same workspace
Hi P108 , Thanks for the clarification. If users can fully open and interact with the reports in the Org App without any errors, then Power BI is already providing the required access for report consumption, even if explicit permissions are not visible on the underlying semantic model itself.
However, if reports or visuals are failing with semantic model access errors, then the deployment pipeline/Git deployment detail could be relevant, especially if the reports and semantic model were deployed or rebound separately.
If that is the case, please verify that the app was republished after deployment and confirm the reports are still correctly connected to the semantic model in the target workspace. Also check whether any RLS roles or composite/chained semantic models are involved.
Kudo CommanderHi,
When you share an app, your audience automatically receives Read permissions on the underlying semantic models to view the reports, but they do not get Build rights by default. In the Manage audience access pane of the app, expand Advanced and enable “Allow users to build content with the semantic models in this app.” This setting grants Build permissions on the models included and lets your users connect to them from the Dataset hub or Excel.
If the semantic model is stored in a different workspace, the app cannot propagate Build permissions across workspaces – you need to add the users to that workspace as at least Viewer or explicitly grant them Build on the dataset. Also be aware that if the model uses row‑level security, users must belong to one of its RLS roles to see data even when they have Build rights.
Hope this helps!