Airtable is a powerful platform for organizing and managing data, but sometimes it's necessary to restrict editing for certain users or categories of users. The ability to block editing at the record-level or cell-level would greatly enhance the security and integrity of data stored in Airtable. This feature would allow administrators to specify which users or user groups can edit or view a record or specific cells within a record, based on the value of a specified cell. For example, if a record represents an invoice or bill that has been paid, the administrator could prevent any further editing by users who are not authorized to modify paid invoices. This would ensure that the data remains accurate and protected from accidental or intentional changes. Use Case: An organization uses Airtable to manage its financial accounts. Once an invoice is marked as "paid," the administrator wants to prevent anyone other than the accounting department from editing the record. The administrator sets up a rule in Airtable so that when the "Status" cell of an invoice is set to "Paid," only members of the accounting department can edit the record. This protects the integrity of the financial data and ensures that only authorized users can make changes. ... View more

What is the proposed idea/solution? What's existing is that when clicking the + button on a "Link to another record" column, it shows a "search box" and we can find an existing record, but you can only search for the linked record's value. It would be more efficient to be able to find an existing record using its other parameters (maybe the four columns that are shown). In the example image below, if I type "Notes C" or "1335", it should show Item 3. What's currently happening is I should strictly type "3" or "Item 3" to get to that linked record. It's especially inconvenient if it's a lengthy SKU or something like "A Very Long Title Like This and That Vol. 3" when I could use that linked record's other columns to find it. How does it solve user problems? It allows the user to quickly find a linked record through other parameters and makes workflow more efficient. How was this validated? The first four columns on the find field are the linked table's first four columns too, so if the user wants to "customize" the first four columns, they can trigger "Limit record selection to a view" when making that linked record column to use that specific view's first four columns. Who is the target audience? Users who use linked records a lot with multiple useful columns. ... View more

What is the proposed idea/solution? Make Interfaces available on the iPad How does is solve the user problems? In construction, we use iPads for most of our inspection and statusing. To not have an interface useable on the iPad app is a major barrier to being able to use this in the field.  How was this validated? ... Who is the target audience? Anyone who uses Airtable not sitting down ... View more

What is the proposed idea/solution? Add a sorting option to the Group function associated the Record List interface (for example.) This option would be available when grouping by a Single Select List and would allow you to order the groups the same as they are ordered in the list. How does is solve the user problems? Currently you can sort Groups alphabetically or reverse alphabetically. This prevents Groups from being a useful way to organize sequential groupings of data, or results in the user including the sequence in the name of the group (e.g. "1. Shutting down warp core"; "2. Disconnecting primary coupler", etc), which is not ideal to manage and may be confusing if the field is used elsewhere in the interface. record_list.jpg shows the interface's record list with the groups collapsed so that you can see the order (alphabetical) single_select_list_order.jpg shows the order of the list and the order I would like the groups to appear group_sort_options.jpg is where one might expect to see another sort option. Tight fit! Thanks for your consideration. ... View more

It would be helpful if I am able to hide tables when they are not necessary for everyday work.  ... View more

I have multiple bases in a workspace and some of them are related, even having synced tables, and other have nothing to do with the others around them. Folders would help organize my workspace. ... View more

What is the proposed idea/solution? Make workspace / base owner able to delete comments on records made by other users. How does is solve the user problems? As base manager (owner), I would appreciate the possibility to remove comments made by others on records without asking each person to delete their own comments. Some of them, furthermore, are not on the team anymore (no more access to base). How was this validated? It wasn't, was it? https://community.airtable.com/t5/other-questions/delete-comments-made-by-other-users/td-p/143650 Who is the target audience? Workspace / base owners. ... View more

What is the proposed idea/solution? It would be great to be able to toggle between different views  whilst in an expanded record.  How does is solve the user problems? Being able to update various relevant fields whilst in the same record without having to make 100s of fields visible can be a huge time saver. How was this validated? ... Who is the target audience? ... ... View more

I find the interface button action [run an automation] to create a linked record with more populated and linked fields than the add record in fields more helpful. I believe it would be very helpful to create an action to then go to that newly created record in the interface as an immediate next step. Either that or allow for additional button actions. ... View more