What is the proposed idea/solution? Currently, there is significant differences in features across the different interface 'types'.  Even among the 'elements' there are differences.  For example, you can have a 'list' type (which has 'sort'), but if you add a 'list' element to another type (e.g. Dashboard), you don't get same capabilities (e.g. 'sorting', 'hierarchy').  It's as if all the 'types' are developed separately, and new features are not retroactively added to 'old' types.   How does is solve the user problems? These inconsistencies in look and features are frustrating to builders who would expect that features are similar across elements.    ... View more

What is the proposed idea/solution? Allow for 'sort' feature in interface types beyond just the full 'List' type.  Lists are available to add in 'Dashboard' type and when added to 'blank' but no sort function is available.  It would be really nice to also allow users to select columns to show/hide in lists.   How does is solve the user problems? Adds much more customization to each user and their different work styles.  Also makes 'lists' more consistent across interface types.    ... View more

What is the proposed idea/solution? Add the comment bubble icon that indicates that a record has comments (or allow it to be turned on / off as a field) to the Card view when displaying How does is solve the user problems? Within a large list of records / tasks, you'd be able to see which ones have comments associated to them  How was this validated? A question from a design team member Who is the target audience? Users of Interfaces as production / productivity tool ... View more

I use grouped records quite a bit but I find the default display format quite distracting and difficult to read because of the field names and the extra space they create, especially when using subgroups. They aren't really necessary because the values indicate what the columns represent. I'm hoping you will give us the option of displaying the field names or not, for each group and subgroup.  Example attached. Thanks for your consideration! ... View more

Right now, Airtable's permissions are not customizable enough for a diverse work environment. I believe it would be beneficial to allow people to choose what permissions are allowed for specific users.  For example: I could choose to give someone the ability to add records, but not delete them.  ... View more

What is the proposed idea/solution? The automations list should be searchable by automation name. When there are lots of automations, finding the right one is annoying, even when organising them in sections.  How does is solve the user problems? Faster access, better experience. How was this validated? I struggle daily with it, and hope others find it useful, too. Who is the target audience? All Airtable devs. ... View more

What is the proposed idea/solution? It's REALLY ANNOYING having to duplicate automation to account for both scenarios. How does is solve the user problems? It's REALLY ANNOYING having to duplicate automation to account for both scenarios. How was this validated? It's REALLY ANNOYING having to duplicate automation to account for both scenarios. Who is the target audience? It's REALLY ANNOYING having to duplicate automation to account for both scenarios. ... View more

I would like the user to be able to drag the edge of the Side Sheet in the interface to expand them slightly. I could use the full-screen page style, but I do like being able to see the records in the background for quick access to them. Not sure what the limitations of implementing this are. But it is something I instinctively try to reach for every time I open up the side sheet, only to realise the functionality isn't there haha ... View more

What is the proposed idea/solution? When you add a button to an interface who's action is "Update Record", you can select a user field and set the value to the dynamic data of "Current User", allow for things like a button to approve a record.  You can also set the value of other field types, like a date/datetime.  However, there is no equivalent option to set it to the current time.  Should allow that as it can record the time a button is pressed.  How does is solve the user problems? Makes approval workflow examples, or any other update triggered by a button press, more robust by automatically recording the time it was triggered.  How was this validated? Created a button on a form interface, set to update record, added a date field and you can only set a fixed datetime value not a dynamic one like "Current date/time" Who is the target audience? Anyone using the new forms interface to build record review/approval workflows.  ... View more