Forum Discussion
Helper ICross‑workspace shared dataset: users must open App A before accessing App B — How to Fix?
Hi v-aatheeque ,
I've just unpublished the app A. So, automatically, the read+build permissions given through the app were translated into grants for the dataset.
Thanks for your support
Community SupportHi Marc_B
Murtaza_Ghafoor Thanks for your prompt response ,In addition to that
Even if App B is shared with the entire organization, access to the underlying dataset (in Workspace 1) is not automatically granted. Opening App A works because it provides users with the required dataset access.
Deleting App A will not break the dataset itself, but users will lose that implicit access, and Report B may stop working for them.
To support org-wide access to App B, you’ll need to either :
- Keep App A published (as it enables dataset access) or
- Grant organization wide permissions directly on the dataset (if allowed).
Note : Microsoft recommends centralizing datasets in a dedicated workspace and granting permissions there, so reports in other workspaces can be shared without dependency on another app.
Reference : Build Permission for Shared Semantic Models - Power BI | Microsoft Learn
Introduction to Semantic Models Across Workspaces - Power BI | Microsoft Learn
Hope this helps!!
Thank You.
Helper IHi v-aatheeque ,
thanks for your support. Maybe I didn’t fully understand your answer, so I’d like to clarify that Report A is shared (granting Build permission) with the specific user who developed Report B.
By checking the Manage Permissions panel of Dataset A, I can confirm that it is shared with the entire organization through the app audience setup, and it seems I cannot add the entire organization also as a user separate from the app audience in this panel.
Thanks
- v-aatheeque
Hi Marc_B
Thanks for the clarification, your understanding is correct.
Even though the dataset is shared org-wide via App A, that access doesn’t fully apply to cross workspace reports until users access the app at least once. That’s why opening App A makes Report B work.
Deleting App A won’t break the dataset, but users may lose access to Report B unless another permission path is provided.For an org-wide scenario, keeping App A published is currently the most reliable approach.
- Marc_B
Hi v-aatheeque ,
thanks.
I gave read & build permission to dataset A through the app to the developer of report B. He shared the app B with the entire organization. Now, if I share directly with him the report (with read & build grants) and remove the app A:
- the model B won't be broken
- the app B ordinary users won't lose access
Is this correct?
Can you clarify on why you believe that keeping app A is the most reliable approach?
Sorry if I come across as nitpicky, but some doubts aren't simple to resolve. Thanks- v-aatheeque
Hi Marc_B
You’re thinking about this in the right way.- Report B won’t break : It queries Dataset A directly and that dataset lives in Workspace 1. Apps don’t own datasets, so deleting App A doesn’t delete the dataset.
- App B users won’t automatically lose access : As long as you’ve explicitly granted the developer (ideally the org-wide audience) Read + Build permission on Dataset A, then App B can continue to function without App A being present.
- App A ensures :
Dataset A is exposed to the entire organization.
Users automatically establish access when they open it.
No need to manage dataset permissions individually.
Hope this helps !!
Thank You.