Permissions For Related Tables In Different Applications Don't Restrict Access As Intended

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered

Long story short, finding that many of my contacts have cross relationships with many apps I have constructed, so instead of having multiple Customer Tables, am working on making one master CRM table and building relationships to it from the various project applications.

However, not to get in too much detail, I have established an "everyone on the internet" user (public) on my CRM with restricted field access, and with no access to "create records"

Now in one my of test app's that I have created a relationship back to the CRM app, using standard record picker and setting myself as a public user, at the end of the records that I can select from, is the opportunity to "add another user", and when I click on it, it opens the CRM "add a record form" even though on the CRM itself I have specified public cannot add records?

Can anyone explain this behavior?  What am I missing. 

Photo of JRogerson

JRogerson

  • 490 Points 250 badge 2x thumb

Posted 4 years ago

  • 0
  • 1
Photo of JRogerson

JRogerson

  • 490 Points 250 badge 2x thumb
Ignore.... instead of changing the access, I signed right out of Quickbase, then reviewed the form as "public" and the offending opportunity to add a record to the parent table was gone.