Relating Parent Record to Child Records Across Applications

  • 0
  • 1
  • Question
  • Updated 1 year ago
  • In Progress
  • (Edited)

I have a table ("Resources" (e.g., employees)) in a table ("Staff Resources"). I would like to have our staff relate the "Resources" to a table ("Properties") in another application ("RMIS"). However, I do not want our staffer to have access to confidential information in RMIS. Is it possible to relate a Parent ("Resources") to a Child ("Properties") across applications without sharing any further rights? See diagram for clarity.

The ultimate goals:

1. Relate Resources (Parent) to Properties (Child)

2. Enable staff to edit Resources-Properties relationship from existing Properties records. (New Properties records can be setup by a different staffer in RMIS)

3. Enable reporting of Incidents as grandchild to Resources

Photo of Devin


  • 362 Points 250 badge 2x thumb

Posted 1 year ago

  • 0
  • 1
Photo of Matthew Neil

Matthew Neil

  • 31,698 Points 20k badge 2x thumb
In order to have access to 'cross-app' data, the user needs to belong to both apps.  

However, a good way to manage the permissions is to make a new role for those 'limited' users so they can only see the bare minimum.
Add a bare dashboard too and hide everything else.

It might be worth setting up a 'group' to have all these cross-users belong to a group to more easily manage.

(Generally I try to keep everything in one application, and then manage the permissions all on one spot.  Makes it much easier to manage and troubleshoot from the admin side of things)

Matthew Neil - Product Specialist

I thought that when a user does not have access to the "other app", then they get the access level specified in the setup permissions of the cross app permission on the "other app", under App Properties and then Cross App Relationships.  That way the lookup fields will still work even though the user may not have any access to the "other" app.
Photo of Devin


  • 362 Points 250 badge 2x thumb

So... this issue has confused me after some serious blueprinting of options and limitations in Quickbase. I had setup another conversation and just posted much more detail on the issue:

I created diagrams (see comments in the other conversation) of each scenario I could think of which might get me closer to the goal but without adding significant workload/data/relationship management.