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 

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.

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

Hi v-aatheeque ,
so if I:

1_remove app A

2_give developer B Build access to dataset A through a direct link

then the report B won't break and the app B audience will continue to be enabled for report B.

Am I right?

Thanks

  • Marc_B's avatar
    Marc_B
    Icon for Helper I rankHelper I
    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 update,

    Yes, this behavior is expected. When the app is unpublished, permissions granted through it can persist as direct dataset permissions, which is why App B continues to work.

     

    Glad to hear everything is working as expected now! If any of the responses helped, please consider marking it as the solution so it can benefit others facing a similar scenario.

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

    Hi Marc_B 

    So your statement is correct for Developer B, but not yet complete for the entire App B audience.


    1. Report B won’t break.

    2. App B users will only continue to be enabled if Dataset A permissions are explicitly granted to them (not just to Developer B).

    That’s why App A is often kept around, It automatically exposes Dataset A to the org without you having to manage permissions individually.


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

    Hi Marc_B 

    Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further