Upcoming database upgrades. Airtable functionality will be reduced for ~15 minutes at 06:00 UTC on Feb. 4 / 10:00 pm PT on Feb. 3. Learn more here
Dec 11, 2020
I’m working on a new project that has a reasonably simple structure:
People table where employees and clients are tagged as such
Employees: can belong to one organization, can see all of their client records, but not all org level clients
Clients: have a one-to-one relationship with an employee and organization
Meta Data: 5 or 6 other tables with various data like courses, assessments, task list etc
an org admin can see everything about all of their clients
an employee can see everything about the clients they’ve been assigned to (and they can add courses, - assessments, tasks etc, to a client profile)
a client can see their own stuff only
Basically the approach I was thinking of was to create join tables for all of the meta data tables like this:
I’ll be using Stacker for the front end so I’m a bit limited with using views and filtering with dynamic variables.
Dec 11, 2020
Great platform. I would make sure the folks at Stacker advise you because they deeply understand how to configure bases to deliver the best possible UX given your base design choices.