What is the proposed idea/solution? Provide an option to opt out of the new user onboarding flow. Stop forcing the flow to pop up every time we navigate to a new page. How does is solve the user problems? It prevents users (like me) being extremely irritated when trying to just get on with doing what I need to do. I've used Airtable before, like many others.  How was this validated? I personally have designed and implemented similar new user onboarding flows. It's also just a poor UX, because it doesn't provide users with the agency to navigate and use the product according to their needs - it forces users to complete flows according to Airtable's unvalidated needs. In fact, how did Airtable validate the need to persist the flow, rather than providing an opt-out? Who is the target audience? Every single new user. ... View more

When building an Interface, we have to manually set every single field to "editable". It would be more efficient to being alble to do this for all fields in 1 click, eg with a slider.  ... View more

This would go a long way in letting many of us move completely away from Trello, Asana, Etc. into Airtable. I know there are workarounds (link to another table’s list containing the tasks), but that quickly becomes overly cumbersome. Would love to have simple checklist as a field option! ... View more

The organization of bases within a Pro workspace is insufficient. Naming and/or color coding is not enough. As the number of bases increases, you need to archive old data or may wish to logically organize bases into groups (or collections), for the growing volume of bases. Can we please have a better user experience to group bases. Airtable has an existing analogy for this with “sections” that group views. At an account level, we needs similar functionality to group bases. My recommendation is that these be called "collections". This capability would enable workspace administrators to better see and organize their collection of bases. ... View more

So let me get this straight… everyone who uses Kanban view and actually sorts their records ends up seeing this same screen as the introduction to their view because AirTable won’t let people hide Uncategorized from view? Whose idea was that? ... View more

Since the interface is a better tool for scalability and training, it would be extremely helpful, like showing labels, to show field descriptions. I figure this would only be needed if there is a need to show the label. I imagine it something like this: ... View more

Some interfaces are made for data entry that requires copying a lot of items, and it would be absolutely helpful to have a little Copy to clipboard button instead of highlighting text and copying multiple times. This is especially helpful if: it's a link or an email—this feature will avoid accidentally clicking on them if done manually it's an editable field that usually requires copying than editing—this feature will avoid mistakenly editing the entry As my suggestion title implies, this is a toggle, allowing Interface designers to show or hide this option. It can also show up when hovered. ... View more

Hello, The automation fields don’t currently allow calculations in fields. For example, I want to create an automation that pulls the date from a selected record and adds or subtracts a number of days from that. It would be a very useful feature to automate some project tasks without having to manually enter the dates. I’m giving an example with dates but automation would be largely enhanced if we could use formulas in fields. Thank you. ... View more

What is the proposed idea/solution? Currently, there's no way for an element (i.e. a Kanban element) to be connected to multiple filter elements. This would be useful for example if a user needs to create an interface with multiple sections. The interface having a main general filter affecting all the elements in each section, and each section containing secondary particular filter elements. The connection here would be "AND" between the filter elements. How does is solve the user problems? This would allow making the interface much simpler, instead of repeating the same filter elements over and over again across all the filter elements of the page, a general filter would be set at the beginning of the interface and the following optional/secondary filters would be left for each section across the interface. Currently the interfaces with this approach are super repetitive and a user needs to apply a single filter multiple times.   How was this validated? ... Who is the target audience? ... ... View more