Granting Access to a Parent Table Through Two Different Lineages

Hi Adam,

Are you using lookup fields to pass the values from Aspen Students to Student Athletes?

Yes. Aspen Students is the parent and Student Athletes is the child.

Excellent.  So to further clarify the issue you are contending with, lets say for example that you have a field in Aspen Students called Emergency Phone Number and you have created a lookup field in the Student Athletes table to pass the Emergency Phone Number field to child records in the Student Athlete table. Finally lets assume that you have add the Aspen Students - Emergency Phone Number field to a form or report visible to your end users.

Is the issue that your end users can see the Emergency Phone Number field when viewing the Aspen Students record, but cannot see it when viewing a related child record in the Student Athletes table?  

If the above is true, then lets determine whether as the application administrator you can see the fields in both records or if it is also "hidden" . If the administrator role can see the field, then we have confirmed that it is in fact a permissions issue for the end users rather than a database relationship or form design issue that is preventing your end users from seeing the information.

To your first question, yes. The issue is that my end users can see the Emergency Phone Number field when viewing the Aspen Students record, but cannot see it when viewing a related child record in the Student-Athletes table.

However, this is only the case for some child records on the Student-Athletes table. Users can see data in the Emergency Phone Number field for student-athletes that they have access to through the Schools --> Aspen Students --> Student-Athletes pathway. But they cannot see data in those fields for student-athletes that they have access to through the Schools --> Teams --> Students on Rosters --> Student-Athletes pathway. In either case, data in the Emergency Phone Number field is consistently visible/non-visible on all forms and reports.

To clarify a little, users are associated with specific records in the Schools table through a field called Assigned User. I'm trying to trace that field through the schema to the Student-Athletes table using lookups or summary fields as appropriate so I can use it to determine permissions on the Student-Athletes table. I believe I'm making an error in how I'm doing this since one pathway works and another does not.

And yes, as an administrator I can see data for all fields and all records in both tables.

Thank you for your help!

You're welcome Adam,

I wish I could provide some additional insight to help you track down the permission conflict. 

Adam,

In my experience, you can never grant Role Permissions to view a Parent by virtue of having permissions to view the children. Ie by using a summary field and then Tying the Role Permission for the parent to that summary field. Quick Base calculates Permissions from the parents down to the children, so conceptually (based on my experience) if it can�t see a parent, then it can�t see the relationship down to the children so it can�t see the summary fields in that relationship.

The work a round might be to have to allow access to all Students, but then to use form rules to hide huge sections of the form, if the user should not be seeing that student because that student is not in the usual school. Then you need to also ensure that users cannot modify reports at all so they can make their our personal dump of all students at all schools.