Long-time fan…yet… this one thing has always perplexed me… Why can someone that ONLY has ‘view access’ to a base… can then go duplicate that entire base with all the records and then become the owner of it… all while having no audit trail of who did it. I don’t know about you but I put lots of time building my Airtables… building out custom workflows, app dashboards, syncing tables from other bases, in-depth field descriptions, specific views and putting accurate information in there to collaborate, communicate and grow with others. It is IP that an organization builds, putting countless hours into perfecting… yet anyone with ‘view’, ‘commenting’, ‘editing’ or ‘creator’ access can take that IP with no accountability. Basically, I would like to significantly reduce who has access to 'duplicate a base’ Only the 'Owner" access should be able to duplicate the base: not the creator, editor, comment or view access. Additionally add an audit trail to who duplicated the base. Maybe even giving specific users ‘this person can duplicate or not’ but I think the owner simplification would be more than sufficient. Without this option, it is such a security shortcoming that it limits the number of users I have using Airtable. And I want to tell everyone in the world about Airtable… Airtable has given me a way to organize my thoughts / systems that I didn’t know was possible. I love the origin and root behind open source programs but please let me have the option to make it open source or not. That is like someone having access to your CRM and with one button, can duplicate all customer records and how they all interact with each other. User Story As an account admin I would like control of who can duplicate our base and it’s contents. if someone can duplicate, I want a record of who did it and when. Resources I am aware of Duplicating Bases - No mention on how to avoid this Yes I know you can send over ‘views’ to people to mitigate this issue… you can send over forms so they can add records to it… grids / galleries with only the information they need to know. I desperately hope I am wrong and this indeed is actually a possible feature that I have missed. With appreciation and admiration for Airtable & it’s community, Paul ... View more

It would be extremely helpful if you add the export and share features to the area of the blocks. Currently, a screenshot is not helpful since numbers are not displayed in the graphic, so it won’t be captured by a screenshot. ... View more

In scripting block, when calling input.textAsync("Your Name") it would be convenient to have an optional second argument to provide a default value in the text field: input.textAsync("Your Name", "Jane Doe") ... View more

Apologies in advance, if this has already been recommended or if this feature already exists, and I just missed it. Currently, when editing the permissions on a specific field, the two exceptions for editing a field are for allowing fields to be set through forms and allowing fields to be modified by automations as shown below. I think it would be beneficial to have a 3rd slider in here for the option to allow fields to be modified by the scripting app as well. Considering that the slider for automations already exists and scripts can be made within an automation, I feel like this would make sense. As a personal example of how this could be beneficial, I have a field in one of my bases that is a list of keywords for a record, used to reference, and search on a record. This list is a comma separated list of words and phrases. I don’t really want someone going and trying to edit the list manually, so instead, I created buttons, one for adding keyword/s and one for removing. Both of these buttons prompt scripts that will direct the user to add and remove words accordingly. But, in order for them to use these scripts, the field must have permissions that allow their account, depending on what their permission level is, to edit that field. Another example I can think of as being beneficial would be if someone had a script to process certain data in a base according to a set of rules within a script. They may not want a user to edit a field manually, but they are okay with the user running a script that modifies the field. I feel as though this would be beneficial in terms of permission setting and security within a base. Thanks. ... View more

When I share an Airtable, I don’t want to put every information visible in the card but also I don’t to show every field in the expanded record. It would be great to have a middle ground where I could sensitive hide fields in the expanded record. Please consider having this possibility as our use case for Airtable is lost without this feature. Thank you ... View more

In many different areas of Airtable, important fields have their information completely cut off. You can see this with calendar views, gallery views, kanban views, forms, and linked records. Below is an example of a cut-off linked record. What year is the linked record? Is the time of the linked record AM or PM? What makes this kind of absurd is that Airtable actually KNOWS that these are date & time fields, but Airtable itself doesn’t even give enough room for its own date & time fields to display properly. ... View more

I’ve created a bar chart with stacked data and I’m looking for a way to add the total to the top of each bar. Seems like this would be a basic function but Airtable Support has informed me that this is not available. Has anybody else run into this issue and found a work-around solution? Thanks! ... View more

Currently if a formula field will return only a date or a number, Airtable will have formatting options for that formula field. However, if the formula will return a string or might return a string, or might return anything other than a date/number, there are no formatting options. Sometimes I write a formula so that it will usually output a date or number, but will return a string if an error condition is met. For example, a formula might calculate the number of days between two dates (a number) but output a string if the end date is before the begin date. This product suggestion has multiple parts to deal with these situations: Allow formulas to output errors which are distinct from the calculated value. For example, if a formula calculates a negative number, but negative numbers are not allowed from a business logic point of view, have the formula report an error that would be recognized as an error, not just another value. This would be similar to the #ERROR message, but could include a human readable string saying what the error is from a business logic point of view. Once formulas can report errors as errors, many formulas that sometimes return strings could then be considered to always return a number or a date or an error or blank, and thus could have formatting options. Increase the formatting options for formula fields to include formatting options for all the formula types. For example, a formula could be formatted as a centered check box (not just a left aligned emoji), as a rating with stars, as a select (with the colors of a select). ... View more

Please consider adding the table UI as an option within your app for iPad Pro (at least the full size model), a la your desktop/browser UI. Thank you, A. ... View more