To whom it may concern, An enhancement suggestion from Kalypso: When using the Date Dependencies settings, Start dates (And due dates if a Duration is already set), should auto populate when a Predecessor is selected.  Currently, dates are not initially set by selecting the Predecessor and invalid dependency error is displayed which is not fixed by opening and selecting Fix all However, the dates are updated if, after setting the Predecessor, the date of the Predecessor is modified or the Due or Start dates as manually set Screen shot after having entered a Duration and selecting Predecessor.  Selecting View All for the 1 Invalid Dependency error and selecting Fix All has no effect. However, if I update the date in the Predecessor, or select a date in the dependent task, then the dates are displayed.  Here I changed the date in the Predecessor and the dates in the dependent task populate.  Here, (after undo), I have selected the start date of the dependent task.  Neither of those solutions should be necessary. Expected Benefits: More efficient and less confusing data configuration process for project schedules that utilize Date Dependency features. Please consider adding this capability.  Regards, Jason Knighten ... View more

It is possible to impersonate a user while building/previewing Interfaces. Unfortunately impersonation is limited to the visibility of records, but doesn't consider the impersonee's permissions. E.g. an admin that impersonates a read-only user can still change the value of a field through an automation triggered by a button. Respecting the impersonee's permissions at least in preview mode would be very helpful for building interfaces. ... View more

It would be nice to be able to customize the content of tooltip in Interface charts by selecting another fields to be displayed in the tooltip. ... View more

Yes, that's the idea. Allow my to buy more storage for my paid Team plan.  I'm even willing to pay! But I only value the storage, not everything else that comes with moving from Team -> Business (that move just to get an 80GB storage for $300/yr seems rather...hmm...excessive; I'll try to ignore comparisons that Dropbox offers 3TB for free). I'm a simple user, and quickly hit the AT 1GB limit in just a couple weeks of learning to use the service, and have one Base. The 1GB is a low storage amount, but I somewhat understand it...Free is really a trial plan, no problem. I liked AT and wanted to continue, so had to move up to Team ("For teams building apps to collaborate on shared workflows"). I don't mind paying more just to get storage, but the 'Team' is just me and my cat. Team could be also described as "For individual users that need more storage" and 'Business' described as "For individual users that need a bit more storage." Point is, it really doesn't make much sense to not allow individuals (and actual Teams) to purchase additional storage (which I understand from another thread is provided by Box). One day maybe I'll reach where I require other functionality, but I suspect I'll go through the Team level of storage (20GB, which is easily reached in my work, which is based on the Museum template) before I need more functionality, and then will have to think about another solution. Quite the bummer to not create a Free-Good-Better-Best pricing structure where your limits aren't based so much on feature differences, but capacity. A pricing model like this gets implemented as AT wants to use this lever to get companies to move to the next tier, so it tells us that a lot of users care more limits such as storage versus features. If AT doesn't want to be in the storage-adding business that is OK, but it would seem that then the ability to point to attachments held elsewhere would be a requirement. And I realize from the Community that AT doesn't read these comments or respond, so this post is indeed for cathartic purposes only.  ... View more

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'd love to be able to designate universal variables that could be referenced from any table in a base. So, for example, if I have a sales tax rate of 8%, I'd like to set that sales tax rate in one single place and then be able to reference that in formulas across the entire base. Currently, if I want to set up this type of variable, I need to 1) create a table of variables then 2) make sure every single record in the other tables is linked to the variables table 3) add a lookup field to every table that looks up this universal variable 4) create a formula which references this variable in the lookup field. For each universal variable, one should be able 1) give it a unique name that could be referenced in formulas across the entire table 2) set a data type (number, currency, percentage, etc) Then, if the sales tax rate changes, I just update the reference variable, and the changes propagate to all the formulas in the base that reference it. It's true that this could be done with manual copy paste or automations, but that's a LOT of work or automations for a very basic bit of functionality. It could easily eat into an automations cap on an AirTable plan. I imagine that it is pretty easy to script for someone who knows how to code, but that's a lot of work (or vendor cost) just to set a variable. I'd love to be able to tell AirTable: "I'm creating a universal variable called "SalesTax". It is a percentage variable." Then enter the number 8% and be done.   ... 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