Building multi-company system with Airtable, db design

[0800-grizzly]

Hi,

So far we've been building a small CRM for internal use. Out of curiosity I started wondering if it would be possible to re-design it to support other companies. I've seen multi-company databases having an owner identifying prefix to fields, e.g.

• company1_project
• company2_project
• company1_e-mail
• company2_e-mail etc etc

For users there's the abstraction "current user" but haven't seen anything like "current organisation" as an access role qualifier. How would one build any access right system hard limiting any access to the user's own organisation.

Would this be at all possible to design? Or would one need something like Bubble on top? Which then would take away the whole point of Airtable, and suggest doing everything from scratch within that environment, non?

Rgds,

Björn

[TheTimeSavingCo]

Hmm, if you were to build it in Bubble, or any other third party portal, you'd need your data to be tagged appropriately and be filtering a user's access off of that, right?

The Airtable equivalent would be using one Interface per org where the appropriate data's filtered I reckon.  Definitely more work than a simple 'If [User] then show [Data]', but still workable if you don't have a large number of orgs that changes consistently