Forum Discussion

Marc_B's avatar
Marc_B
Icon for Helper I rankHelper I
5 months ago
Solved

Cross‑workspace shared dataset: users must open App A before accessing App B — How to Fix?

Hello, I have created a report, which I will call “A”, in a workspace and granted Build permission to a colleague through the app audience settings. He then created his own report, which I will c...
Need Help
  • Marc_B's avatar
    Marc_B
    5 months ago

    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

v-aatheeque's avatar
v-aatheeque
Icon for Community Support rankCommunity Support
5 months ago

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's avatar
Marc_B
Icon for Helper I rankHelper I
5 months ago

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's avatar
    v-aatheeque
    Icon for Community Support rankCommunity Support
    5 months ago

    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.

     

    • Marc_B's avatar
      Marc_B
      Icon for Helper I rankHelper I
      5 months ago

      Hi v-aatheeque ,

      I noticed that the third point seems to contradict the first one. Did you mean to refer to app B instead of app A in point 3? Thanks again
      • v-aatheeque's avatar
        v-aatheeque
        Icon for Community Support rankCommunity Support
        5 months ago

        Hi Marc_B 

        let me clarify :

        Report B won’t break: It connects directly to Dataset A, which is independent of App A.

        Users still need dataset access : Permissions given to the developer do not apply to end users.

        App A is the one exposing Dataset A to users. When users open App A, their access to the dataset gets established, which is why Report B (in App B) starts working afterward.

         

        Role of apps:

        App A - provides access to Dataset A.

        App B - uses Dataset A for Report B.

        Hope this helps !!

        Thank You.