What is the proposed idea/solution?   From the Admin panel, to have an option that disabled everyone that is not an admin from creating new Workspaces. How does is solve the user problems? The issue is that users in our organization create new workspaces, and this turns them into Owners automatically. Then, they are enabled to share access and provision higher licenses to other users, changing our billing. We have documented this issue internally, but our company has hundreds of users on Airtable. Employees join and leave the organization every month, meaning that it becomes unviable to rely merely on internal training. The tool needs to enable admins to protect the billing cycle. How was this validated? We see the issue every other month. Who is the target audience? Enterprise accounts ... View more

Currently, the button field allows you to run an extension script. I have to maintain separate automation and extension script that performs the same actions. Would be ideal to be able to run an automation like interface buttons do. Support for multiple triggers would also be helpful. For example, I could have a trigger for when a record meets certain conditions and a button trigger whenever manual execution is desired. An automation script where I think this would be useful is one that creates or updates a record/object in a third party system. ... View more

To whom it may concern, An enhancement suggestion from Kalypso: Add ability to color code Table Tabs. See attached screenshot for examples where this might be implemented for Kalypso template.  Expected Benefits: Enable easier visual recognition of and/or navigation to related tables. Please consider adding this capability.  Regards, Jason Knighten ... View more

Often users type up their notes, meeting agendas, tasks etc into a Long Text field using Rich Text formatting. The Records Comments field is often a target for copy/paste from that field, especially with Comments Element being so prominent within Interfaces. However, upon copying/pasting Rich Text from a Long Text field into the record Comments, all Markdown formatting is lost. It's most frustrating - and to be honest I expect Comments to support such an action. Here's my Rich Text data; And here's the same data copy/pasted into Comments - note how the Markdown formatting is lost.   ... View more

What is the proposed idea/solution? Other elements, such as Calendar, Timeline, Gallery and Kanban to act as Record Pickers, allowing for records to be clicked within the element, and their subsequent fields to be looked-up and displayed within the interface. Think of the way a Record Picker element behaves, and now apply that behaviour to the other Elements. When you think about a Calendar, it's showing records just like the record picker is showing records, just in a different visual format. Further to these mentioned elements, this same Record Pick behaviour should also be added to Linked Fields and Lookup Fields. How does is solve the user problems? The Record Picker is a very powerful element - but I feel it shouldn't have a monopoly over its specific functionality, and that the other elements such as Calendar etc would all benefit vastly from having this same ability. Who is the target audience? Anyone building and using Interfaces, where multiple tables are in play, typically at 3 levels deep - for example, Project -> (Task Dictionary) -> Task. ... 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

What is the proposed idea/solution? Allow users to assign different detail pages based on conditions. When a user expands a record from an interface, allow users to change which details page opens based on conditions of the expanded record. Setting the conditions could work using a UI similar to the one conditional coloring uses. What is the problem? There are many instances where I have records that share 90% of the same info, but based on some differences - such as Type or Status, need to be interacted with differently. For example, for my business we track furnishings and fixtures we refer to as "Items" for architectural projects. We need to ensure that certain pieces of information are recorded for each Item, but what pieces of information we need varies based on the Type of Item. There are so many different kinds of information that we need to record that we have as many as 120 different fields in our Items Table. ideally, we could show only those fields that apply based on a condition, in this case, the "Type" Field. I.E. If an item is of the "Plumbing" Type we want to see fields like "Fitting Diameter" and "Finish", but for an Item of the "Lighting" Type we would want to see fields such as "Input Voltage" or "Socket Type". Ideally we would be able to see all of the Items in one list, and simply have a different detail page open based on things like Phase or Type. At the moment, the only way to do this is to create a different interface page for each type of Item. This approach does not suit the way we need to organize the Items (Typically by Room), and we need to be able to see all the Items in one Grid or List, but be able to open a different Record Detail Page based on the "Type" Field. How does is solve the user's problems? In the attached images I included a simplified example of a Grocery Order Table. The Orders have different Types, and for each Type I created a Details Page that shows only the relevant fields based on that type. ( I am not a Grocer so forgive my goofy and incorrect examples of data) In the mock Interface Editor UI I made, users create different Record Detail Pages the same way they do now. They can then select an option for Conditional Detail Pages that functions exactly the same way that conditional color works: Users can add Detail Pages they want to open under specific conditions, assign those conditions to each Details Page, and specify their priority order and defaults. When a user clicks on a given record in an interface, which Record Detail Page opens is then dependent on the conditions assigned above. Other Notes: There are situations I have come across where this change would allow me to remove complex linked table set-ups that rely on automations to maintain and create links between records. I have one base where this change would remove around 200 automation runs per day, and significantly reduce the complexity of the base. Conclusion: Adding this feature would make a massive difference to Airtable's overall usability for my company, and would enable a wide variety of new use-cases that otherwise depend on more complex base structures. ... View more

At the moment the form only allows input of new data. Can we have a form for editing existing records? At the moment we can only edit in the table meaning I can’t present the records the way I want. Can’t even hide columns on mobile, meaning the users are free to wreak havoc on the existing data :grinning_face_with_smiling_eyes: ... View more

Hi, I discovered Airtable just a few weeks ago and instantly fell in love with this application. It’s so cool! I am still new to it, but I’m learning so much. However, as a former Access user, I’m surprised it doesn’t feature almost any advanced rules for data input and validation in fields. I’m even more surprised that so very few people are asking for them. Data validation is important. For a solid database, it’s a core feature. Say I want to record a customer’s IBAN for money transfers. An IBAN always has exactly 27 characters; it’s not all right if someone by mistake inputs 25 or 28 characters or puts spaces into it. I need to set the IBAN field’s lenght to 27 characters and request that you fill out those 27 characters, not one less, not one more! Same goes for zip/postal codes, or tax codes. Validation rules are needed for such fields. A lot of stuff can get messed up if this kind of data is not recorded correctly, such as payments, shipments, fees. It’s a serious matter! Phone numbers and email fields should be validated, too, because they should not accept invalid characters. I should be able to set Date fields to accept only certain ranges of data. Such as: “you cannot input a delivery date that is before today”. I can’t even find such a thing as setting a field to “required”. Even though the application is fantastic, these shortcomings are a major kickback for Airtable. Please consider introducing these features, I’m sure many users will be grateful! As I said, I am new to the application so pardon me if I’ve said something wrong or I missed out on issues that have already been addressed. Love ️ ... View more