What is the proposed idea/solution?
Provide a mechanism to identify and flag STALE tables/bases within a given Airtable workspace. Stale tables/bases are those where the data has NEVER been accessed within the last 30/60/90/180 days. Consider allowing base creators to set an OPTIONAL time-to-live (TTL) timestamps either on a per table or per base. If data has not been accessed either by a user or by an API after that time, then auto-delete the table/base.
How does is solve the user problems?
In many environments, there is "data sprawl" where users may randomly create "test" tables/bases for short-term purposes. It would be nice to identify and flag where stale data exists, so that it can be purged as needed. This can be a compliance requirement for many industries, depending on the type of data stored within Airtable.
How was this validated?
Teams can spend DAYS or WEEKS per month trying to figure this out. Having a mechanism like this would save countless hours of manual review.
Who is the target audience?
Airtable administrators
Notes:
* 7 days before a table/base is about to expire, email the creator of the table/base to notify them the content is about to expire. Include metrics about how frequently the data has been accessed in the past 30/60/90 days by users or API calls.
* Provide a quick mechanism for administrators to: extend the TTL by a fixed amount (like +30 days) OR turn OFF the TTL altogether.
