We have multiple clients tied to multiple projects through a series of tables that represent stages within a project and are having trouble showing the nested records within each stage. We can currently only make it two or three tables deep. This nested record access is necessary for restricting user access to their user login. The specific scenario we are trying to model using knack is construction project management where there are many different contractors (table A) associated with many different construction projects (table C) so we created a relational table that groups contractors and projects (table B).
Our verbal UML where {} is the relationship between tables.
User Role Table {many to one} Client Table {one to many} Contractor-Project Grouping {many to one} Projects Table