Welcome to the Airtable Community Product Ideas Board! Help us shape the future of the Airtable platform by sharing your ideas or kudoing suggested features from other Airtable enthusiasts like yourself.
Personally, I like the default color options (despite the limited number) that are provided for the base/interface appearance color. That said, members on my team really wish we could match the exact color of our base with the primary company brand color. I feel like it wouldn't be too hard to have an 'advance' section under appearance that allowed us to input a HEX number.
... View more
The ability to set defaults at levels higher than field: base, workspace, team, user or account level for time zones and date, number and currency formats. For accounts or workspaces where all users consistently work in the same locale that is not the US, it would save base builders a lot of work in setup, double-checking and troubleshooting, and avoid many mistakes caused by inconsistencies and discrepancies for the whole organization.
... View more
What is the proposed idea/solution? Create a banner area or an extension to add a banner area that allows for creator to have a marquee of announcements. View would be available above all tabs, so no matter the user's tab or view, they can see the relevant announcements posted by the creator. How does is solve the user problems? Company announcements can have a constant view instead of being stored in one area of the base. How was this validated? ... Who is the target audience? ...
... View more
We need a way to choose a dynamic latest end date by each record, ideally an optional date field that goes into the timeline settings and does not allow records to be scheduled past that. I've explored using colors but there are two issues: We can't use dynamic values in the color conditions Even if we could, I'd like to combine the conditional coloring with auto-coloring from selects
... View more
Hi, We're using Airtable to progress job cards via a Kanban system with assignee (staff member) as the single select field and task as the record. Unfortunately it only shows the assignee stacks that contain records. i.e. the staff that have tasks. If a staff member has no task, their empty stack is not visible. This makes reallocating tasks to someone without an existing task in kanban view impossible. It would be great to have an option to select which assignee (staff member) stacks were visible including those with no records in their stack.
... View more
What is the proposed idea/solution? ...when changing the name of a Field in a Synced Table, the updated name should also be Synced. This would likely require a feature, whereby a Synced Field and a local Field can have the same name without a conflict. This should not be a problem, because it's easy to determine what is synced field vs local due to the lightning bolt icon. How does is solve the user problems? ...without this feature, any changes to a Field Name are not propagated to other Synced Tables. This causes confusion. How was this validated? ...Try changing the field name of a Synced Table and find out! It's frustrating. Who is the target audience? ...all users who use Synced Tables.
... View more
We use Airtable quite extensively and the most often used tab has a whopping 65 columns. We make use of many views and love Airtable! A small frustration is that when trying to organize columns from the "Hide Fields" dropdown you have to grab each visible column one by one and drag it to the top if you want the visible columns to be first... which we usually do. It seems like this would be something very easy for the developers to add a "Move hidden fields to bottom" or "move visible fields to top" button and it would save a lot of time on a very automatable task. Thank you for your consideration.
... View more
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.
... View more
What is the proposed idea/solution? ...A feature that allows the User to change the Sync Source, similar to a Single Select drop down. This moves the record to the desired Source. How does is solve the user problems? ...Without this feature, a User would need to manually delete the Record form the Sync Source, and add it to the desired Source. Who is the target audience? ...All Users who need the ability to move Records to various Synced Sources.
... View more
