I am looking for some reassurance on how to manage the risks associated with growing number of “Creators” in my base.
There would be a massive operational and financial cost if a key field, table or base was deleted by accident (or by a disgruntled employee).
“Interactive complexity” (multiple components interacting together e.g. here the links between fields/tables in the schema) and “tight coupling” (how close the dependencies are linked and the period of recovery e.g. filters are broken immediately when a field is deleted) means that there will inevitably be an accident over some period of time.
We manage this risk by having highly centralised control of who can be a Creator (only me currently).
When recovering in instances where a field is deleted, the options offered by Airtable don’t really help us:
- Snapshots would only allow returning to an older version but in an entirely new base (thereby not recovering the original base and it’s links to other integrations).
- Crtl z / back / Airtable restoration would return the deleted field but it would not restore the filters where that field was used and any views linked to automation triggers would have released the data. By that point all the automations would have been triggered (eg Make, zapier)
How does everyone else manage with many people working as creators in a base?