Hello,
I work for an online school managing various technologies. Last year we moved away from a traditional Student information system and built a homegrown system in Airtable. This has since grown to a base for accounting, admissions and a support/helpdesk.
I am finding that we did not build out the first version very wisely, and we need to make some changes for better automation and syncing of data.
Is our solution to move these separate bases into one base with each table respresenting one of the groups, or do we leverage the sync bases feature?
I am sure that you may need more information, but I do not know what else you want/need to know to be able to offer advice.
Thanks in advance for any ideas/support.
Both of these options (one mega-base, or synced tables) can work. Deciding between the different options depends on several factors. Here are some of them.
- How close are you to record count limits? If you are pushing the record limits, you may need to use separate bases and limit how many records you sync in.
- Will some people need base access (versus interface access) but they are not authorized to view some of the information? If so, you need to use multiple bases.
- How much edit access will people need? It can be easier to limit edit access by syncing in data that should not be edited versus messing with permissions inside a single base.
1 Like
Beautiful question and a beautiful answer.
Classical tale of a hands-on handyman starting something easy, oh it’s easy like excel, grows into a whale with 7 heads and 7 fins, haha. Been there too:)