What is the proposed idea/solution? The idea is to have a table within the database that stores information about the base's users and is accessible to use for filters in interfaces without having to have copious numbers of linked records across the base. For example, the table outlines the user, their manager, team, etc... then, in the interface, I can filter to check if the current user is in a certain team and show them records if they are. ... How does it solve the user problems? It removes the need to create a multitude of references across the base. I currently, for example, have a user and a team table, and each has multiple reference fields to outline how they relate to others, like their managers, their manager's managers, anyone who should have visibility over this person's records, etc...  This would allow me to instead have the following filters: - if record owner is current user (currently possible) - if current user is in X team - if current user is in leadership team These wouldn't be possible without linking the X and/or leadership team to each record in the table, which isn't very efficient to do, particularly if you have thousands of records. ... How was this validated? Doing a lot of work around the visibility of records within Airtable interfaces based on values in the table. ... Who is the target audience? Bases that have multiple people working in them. ... ... View more

What is the proposed idea/solution? It would be great to have more options for notifications instead of just Email and Mobile on/off. Right now, we have to turn on the ability to be notified for all comments instead of just mentions for EACH record. It would be nice to have the option to turn all comment notifications on for ALL records!! How does is solve the user problems? It would help users not have to remember to turn it on, allowing them to not miss any important comments. ... View more

Feature Request: It would be great if Airtable scripting blocks or button fields could support browser-level JavaScript interactions, including:   window.open() Functionality: Allow scripts or buttons to open external links in small, controlled windows. Custom In-Page Pop-Ups (Modals): Allow scripts or buttons to create in-page pop-ups (modals) that provide real-time feedback, confirmation messages, alerts, or custom input forms directly inside the Airtable interface. This would create a smoother user experience without opening new tabs or navigating away from Airtable. Redirect to Created Record: Enable the ability to automatically redirect users to a newly created or updated record after completing an action (such as a form submission or automation). This would enhance navigation and user flow. Use Case Examples: Fillout.com Forms: I want to click a button in Airtable to open a Fillout.com form in a small window instead of a new tab, similar to Google’s login pop-ups. In-Page Pop-Ups and Alerts: If a user changes the status of a task (e.g., from "In Progress" to "Completed"), a pop-up could appear prompting them to fill out additional fields (e.g., feedback or completion notes) before the change is confirmed. This ensures necessary data is captured right when it’s needed, without leaving the Airtable interface. Redirect to Created Record: After an automation or script creates a new record, automatically redirect the user to that record for immediate viewing or editing, streamlining workflow. ... View more

I assume this is a popular request but I think ELIF functions would be very helpful in making functions easier to write. Nested IFs can get cumbersome and the alternative SWITCH can be difficult given a large set of possible values. Converting single and multi select fields into a logical format would be much simpler using ELIF. This would likely also generally reduce the need for dummy fields used for steps in a larger function.  I find the select fields to be very useful for users and would like to be able to run automations and calculations via select fields but it seems more difficult than necessary. I think ELIF would reduce the complexity.  ... View more

In my experience, tags are things that are added by the user, not by the admin. While tagging photos for example, it's almost impossible to predict what tags will be used. Make it so that I can add items in the multiselect interface. This could be an option in the field definition "Allow users to add options". This would work well with the other feature request I saw on here about showing how many of the other tags there are. ... View more

What is the proposed idea/solution? Add "Prompt" as an answer to "What should each record be called?" How does is solve the user problems? How was this validated? See images above. I wanna use my table as a prompt library Who is the target audience? Er'rybody ... View more

Hello! The search bar in the "Data" section of Airtable should not only function as a search tool but also as a filter, similar to how it is already possible in interface tables. Users could access relevant records faster without having to switch between filters that don't consider all records and cannot be deactivated. Not having to set up the filters again each time would save a significant amount of time. Such a filter function already exists in interface tables and would offer more flexible search and filter options. The irrelevant records still show up, while all relevant ones aren't hidden:     ... View more

I have figured out the update record action on the automations, but the parameters it asks for is so incredibly vague and unclear, it should be corrected.  It should be something like: record to update: field to update: source record: source field:, It allows you to select a record or a field, when it needs a record??????.  I love your platform, but that form (and many like it) are vague to the point of being in the "what were they thinking?" category. Thanks Jeff   ... View more

What is the proposed idea/solution? Airtable base needs a special table (or method) for adding and managing data related to collaborators. I mean this by team members. How does is solve the user problems? Think that you're tracking work hours of your team and everyone can go and add their own hours via interface or something else. Now you should be able to add "global" data related to who has done the record (or marked as collaborator to that data). For example hourly salary, work hours etc. Sky is the limit really. It would replace the "normal" way employees/users are "meant" to be done now. Being able to link that data to collaborator in base level would solve many issues with data linking and keeping them organized. Also it then should be possible to lookup and rollup data based on linked collaborator(s). So basically the "collaborator" field would be just a special kind of link to another record and every base would have this one special table just for them. Or something similar. Who is the target audience? Everybody who use collaborator field. ... View more