###Implication of Current Design
Just wanted to re-emphasise/rephrase what I seem to recall other users roughly stating (@David_Huck 's post might have put this in my head):
In this discussion we have mentioned a few alternative solutions that were approached from very different angles (views, permissions, etc). But the fact remains that the way airtable is currently built encourages people to build multiple bases centered around a particular subject (HR, Accounting, etc). People will be tempted to think this way while multiple bases are made readily available. Perhaps this was because of the templates that were made availible when we signed up for airtable, or perhaps it’s just the way people work. Either way… it IS the current state of affairs.
###Implications of Permission/View centered design
Now, if “we” (and I say “we” because you at Airtable are so good at making us feel part of this process even though ultimately it is your decision)… If we go the route of using permissions/views to solve problem of sharing data, then this brings up many questions:
Does this mean that we will be creating a larger base, organized by permissions/views (as opposed to smaller bases organized by subject matter)?
What, then, will be the purpose of having separate bases?
Even with multiple large bases, at some point you may want to share data with another base… would it not make sense just to put ALL your data in ONE huge base?
We will need to be re-educated on when to create a new base.
If we go this route, then it seems like we are moving in a direction of making individual bases obsolete (or at least less meaningful), and that is fine, but I just wanted to point that out.