Option to Limit the Access to Interfaces. I want to build an App for my co-workers that are not that techie. So i want to keep them from seeing the Base and only allow them to see certain areas of an Interface. Would be helpful for customers too. Sadly there is no way, as far as i can see ... View more

I'm a HUGE fan of interface builder and it's becoming more of a replacement for my day-to-day interactions with my Airtable bases.  One feature that I would like to see added to the Button options is "Open Interface Form".  Below is a screenshot of the current list of options that I would like to see extended.   Because Interface forms offer a much tighter integration with Interface builder (not to mention increased usability and elevated design) it would be nice to have the option to create new records via Interface Builder forms without having to add a record picker and then selecting the option to create new item (as seen in image below) If this feature is already in the pipeline, thank you! If not, I hope to garner enough support from the community to get this feature on the roadmap.   Thanks for lending me your ear and I welcome any feedback / questions. Justin       ... View more

Hello everyone, love your app! Here's a quick suggestion, which might be fast to implement. Sometimes the column name has three or four words, and it's content is just a checkbox or a two-digit number. Could it be that we change the height of the column names, and maybe even word-wrap for it to be as compressed as possible? It could be a single select from one, two, or three rows for the headers, or have it with word-wrap by default. Something like this: -- Includes prime vid YES -- This would be really helpful to show clear information and maximize column space. Thanks! ... 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? Extend the date dependencies feature from only coverind 'date' to also cover 'hours' and 'minutes' How does is solve the user problems? I want to build an agenda for a conference. The records are my sessions (e.g. Keynote 1). Now I wanted to use the date dependency feature to update the whole schedule if I let's say change the duration of Keynote 1. Who is the target audience? Basically anyone who want to build a schedule or running order. ... View more

Hello, I am sure this is a heavily requested topic, so if this is on the roadmap great, if not I really think this process would help a lot of users. I use Airtable for a number of use cases and have multiple builds. One feature that is rather consistently peeking its head is parent child linking. The first time this arose, and my primary use case, is in a contract management system my team and I built in Airtable. The question arose whether or not Airtable can achieve parent/child linking. The general consensus was a resounding "NO." I took this on as a challenge and after many hours of trouble shooting and testing, I believe I created a working two way linking between two or more records in our contracting system that links the parent to the children and child to the parent. This bidirectional syncs allows for various contract managers to work and link the records as they come in. Further, using the OrgChart extension, we can now see the entire contract family in a visual manner.    Now for the downside. This requires 5 separate automations with multiple actions and triggers which causes the linkage to be rather slow. I believe that if this was converted to a native backend process it would be speed up that linkage time and free up automation space in our base. Again if this is already on the roadmap great. However, if it is not and you would to explore the concept and would like to see how this works I am happy to provide a screen recording and screenshots.   Regards, Eljay Higley ... View more

What is the proposed idea/solution? A keyboard shortcut (on Mac) to move from table to table. (Never touch the mouse. Never leave the keyboard.) ... How does is solve the user problems? Moving one's hands away from the keyboard to touch the imprecise mouse is time-consuming. ... How was this validated? Experience. ... Who is the target audience? Anyone that see the value of using keyboard short cuts to say time by not having to move off the keyboard. ... ... View more

What is the proposed idea/solution? Right now when you search for a linked record, only exact results are returned. This means if I have a record titled "Texas State Fair - 2024 - Food", I cannot quickly grab that record by searching "Texas 2024" or "2024 food" because it's not exactly titled that way. I would have to type it all out, including hyphens, and if I had a lot of "Texas State Fair - 2024 - ###" records I'm going to have to look through them all every single time. How does is solve the user problems? Allowing a more relaxed search, semi-fuzzy of sorts, allows faster searching using the details a user remembers. It's very common to have the primary field of a table be a CONCAT formula to gather multiple pieces of data from a record (especially since you can only search for a linked record using that primary field and nothing else). By allowing less precise searches you can make it easier to find results, and there's nothing stopping a user from still being as exact as possible to further narrow down the results if they want. By loosing the tight restrictions, both types of search can still take place, but in the current design you can only use exact. How was this validated? Heavy use of linked records across multiple bases, and no ability to quickly search through thousands of records effectively to find the one I want unless I know its exact name in the primary field. Who is the target audience? Any Airtable user who has a base with linked records, especially if the base is large. ... View more