Forum Discussion

ChristineKirk's avatar
ChristineKirk
Qrew Cadet
6 days ago

App-to-App Permissions/Relationships

Hello!

I am building my second app and trying to tie it into my first -- it feels like it wants to be separate because the users who will primarily use this app are from another department, but there is a lot of collaborative/universal information in my existing app I'd like to be able to share between the two apps, though there's too much in my initial app that the other department should not have access to, so creating a whole separate space for them and feeding in the pieces I do want shared access to feels like the best way, rather than bring them into my existing app and cull back their access.

To that -- A) does that logic track properly? And B) Do they need a relationship to every table I watn them to access, including grandparent tables? I wanted them to see some grandparent info, and I notice when I run tests using them as a user, that since they're not in that other app, they only see throughput from the table-to-table access, and anything that's generating off a grandparent table just won't throughput for them, which is really surprising to me.

Thanks!

 

My view, and then that user's view side by side:

 

 

Relationships
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    5 days ago

    Yes it makes sense to have a separate app.  You might want to consider using Connected Sync Tables to bring in the Tables that the user will need.  These can update hourly which may be often enough for your needs.  That way all the chess control and print Yale's will still be in the app.  It does mean that users will not be able to update the Sync Tables as the source of truth will be in the other app.