As companies grow and evolve some databases should become read-only and/or removed from day to day operations. How are people handling this right now?
I often avoid creating databases in Fibery for small projects or project specific data because there is no way to “Archive” a database or space.
Examples:
When building a custom workspace for a client (in Notion or Fibery) I often map out fields and their functions. When working in Fibery I do this off platform, but I would have just created a database in Notion or Coda where there is no global record of databases.
I build an invoice generator to assist with back-filling records and now I need to sunset it as we’ve adopted a new platform. I don’t want any new records created in the database or old ones edited, but as the admin, I’ll always be able to see it.
I was thinking about this too recently! Adding thoughts:
Fibery is very good at mapping out and working in complex, repeatable processes. But isn’t the tool for ad hoc processes that are one time.
For example, I need have calls and take notes with a few stakeholders. I’m expecting that these calls will only happen once, as we are changing our processes. The stakeholders are already fibery entities, so it makes sense to do it there. The issue is that the new database, and the relations to the stakeholder entity will now still be part of my system, even though the process that it was for is over. Deleting the database would delete historical data, but keeping it makes things messy.
Allowing a middle grown where:
Relation fields on the stakeholder database related to the archived database are hidden and can not be toggled on in any view.
The database gets hidden from search. (Can be toggled back on)