What is the proposed idea/solution? Providing Interface designers with the ability to allow/disallow the visibility of the field "i" tooltip inside Interfaces. How does is solve the user problems? Currently, we are using text blocks in the UI to explain certain field purposes or possible pitfalls of user selections. You can really clean up an interface and reduce user support questions by providing them with the ability to get further information before making a choice at the exact moment in their workflow that it is appropriate. Blocks of text mean to help a user perform functions really make the entire interface too cluttered to use for experienced users. Some users don't use the system very often so they usually completely forget and need this help but. Maintaining two interfaces with different levels of "Info Help" is not a viable option. From an administration standpoint, this allows for already existing documentation to now serve both database designers and end users at the same time. Future leaning thinking also implies that there could be two fields for "Description" - each with a different set of permissions so that admins can leave themselves complex backend notes for themselves and their teams yet provide more simple descriptions for interface front end users. How was this validated? N/A Who is the target audience? Anyone designing interfaces for themselves or others ... View more

Feature request... with interfaces allowing to filter by current user there are some users you want to always allow weather they are linked to that record or not. Would be nice to be able to add and additional filter that said if "current user" is any of...and they you could select users that always have visibility ... View more

What is the proposed idea/solution? At the moment, you cannot readily access the Page Designer through Interface when trying to implement a button. How does is solve the user problems? I would like staff to be able to generate letters in AirTable, but they work out of the Interface, exclusively. How was this validated? ... Who is the target audience? ... ... View more

I really need for Kanban to work with a multiselect field the way Timeline works. The ability to group/lane by each option in the multiselect field. Then if there is more than one selection then the card appears in each lane of the selections. I would think that in the split scenario, if a card is selected with options A and B ... then if you grab a card to move it from option A to Option C, it would result in Option B and option C now. If you needed to add a 3rd selection, then you would go into expanded view to edit the selections. We are using this as a todo/workload board. Anything under a team/persons name indicates it's in progress, and we can see what they are working on and when each are due. In some cases we have a task that needs more than one person working on it, but do not want to create new projects for these scenarios. ... View more

I know this has been posted many times before, but we need a real solution to allow for grouping by multi-select fields in a way that makes all records associated with at least that value shown in the value grouping.  Yes, this might result in one record appearing multiple times in a grid view. Yes, that is desirable.  Notion users know that this is much more intuitive and user-friendly than the way Airtable handles this behavior.  --- Here's a real example for us: We do project planning in Airtable across quarters. Projects may span multiple quarters (multi-select field). There is no way to view all projects grouped by quarter where all Q1 projects are collected in a single group!  As a designer, it boggles my mind that it behaves this way...   ... View more

What is the proposed idea/solution? On Interfaces, I would love for a user to be able to hover over an element and see the set of conditions/filters that are acting on the element.  How does is solve the user problems? I often create dashboards that summarize data for my colleagues. My colleagues are not comfortable going into edit mode to see how an element was configured. Nonetheless, they may be interested in understanding what data a number element, for example, is drawing from. This would allow them to learn that without having to enter edit mode.    How was this validated? Haven't validated it at scale, but I see this as a hurdle for my team regularly. The person who constructed the interface dashboard is the only one who really understands what the various elements mean Who is the target audience? Users of interfaces ... ... View more

What is the proposed idea/solution? If an email field is set to required on a form, the form should not allow the user to submit unless there is a valid (properly formatted) email address entered into the field. How does is solve the user problems? It allows form users to fix issues before submitting a form with invalid data. It helps the form owner ensure that the incoming data is correct. It makes it more likely that the form owner will be able to contact form users and e.g. send confirmation emails. How was this validated? People are expressing their frustration about the lack of this issue on a number of different threads in the Airtable forums. Who is the target audience? People creating sign-up forms or any form where the form submitter might need to be contacted as a result of submitting their info.  ... View more

In the "New " Interface layout, it would be great to "Add elements" like you are able to in the "older" interface layout. It is very helpful when needed to add a list or grid from a different table. It also helps with tasks list or being able to see all the linked records.  ... View more

Today you can add a horizontal line divider. It would be useful to have the same for a vertical divider ... View more