I hope your week is going well. As you may have noticed this morning, editable shared views was accidentally enabled for all Airtable users and has since been rolled back.
First, I would like to apologize for any inconvenience or confusion this may have caused and acknowledge that we know this is a feature that the community is excited about. It has been great to watch people become experts in 30 minutes to share with the community and see all the excitement on Twitter. We know how upsetting it may be that this was accidentally enabled and we want to share some insights into what happened with all of you.
We know that collaboration in Airtable is top of mind for many of you (us too!), and the editable shared view feature is one of the many ways we’ve explored making that experience more impactful. However, we’re not currently prioritizing the development of this feature and are instead focusing on solving this problem in a more comprehensive way.
As Peter mentioned during Table Talk last month, we are planning to do a holistic revamp of permissions and updates to sharing in Airtable and do believe that there’s work to do to make collaboration in Airtable easier, more secure, and more scalable. We want to ensure we are delivering the best possible solution to you to solve this problem and have a team actively working on solutions that we hope to be able to share later this year.
We also recognize that many of you have ideas about changes you’d like to make to Airtable’s collaboration experience. We’d love to hear those ideas in the thread and why they’d be impactful for you. We’ll be taking that feedback, along with everything you’ve shared related to this problem in the Community in the past to help guide our future thinking.
Thank you for your understanding, we really appreciate it and apologize again for any confusion.
Does Airtable has any idea how ridiculous we consultants will look to our clients now? I for one informed most of them immediately because everyone is waiting for this kind of functionality! This is really not ok, seriously, Airtable has lost so many credit the past months and now this, which is directly affecting our client relations.
I know this is not your fault, but as a rep for Airtable in this community, I want to make clear how p**** off I am. And this is imo not appropriate…
Jordan, thank you for posting this. Trying to get the wording right in a situation like this is so hard.
It is also good to hear the reminder that Airtable is working in the background on revamping the permissions model, and that we can expect major changes related to this in the future. There is a lot of invisible work that goes into overhauling permissions.
I hope that the community will be educated about the changes before this major revamp of permissions is rolled out that the community.
In fact, can we get an overhaul of how Airtable communicates feature changes in general? If Airtable had been in the habit of announcing a feature change somewhere at least minutes before rolling out new features, we could check to see if changes we see are a bug, a mistake, A/B testing, or an actual feature change.
Can you also please clarify who currently is able to get access to the editing of shared views? Prior today, selected enterprise users were able to get access to this feature. Is it still possible for enterprise users to request access?
What should people who have already created editable shared views do with them? Will these editable shared views continue to function?
This is the second time that I’ve seen you open a post like this and I’ve thought: poor Jordan, her week is not going well because she is forced to set aside whatever else she was working on to write this post.
I don’t have the energy to get into how bullshit this is. Getting really tired of airtable. Not the product. The company. Probably one of the least organized I’ve ever seen. This is extremely embarrassing.
Welcome to the Airtable community! It seems like you joined this community just now in order to post to this thread. Would you mind posting an introduction?
I hope that Jordan knows that I wish her the best and do not expect immediate answers. In her post, she invited people to post their ideas “in the thread” and I replied with that in mind. Do you feel that my questions/comments were invalid or better suited to a different venue? If so, please clarify.
@Databaser totally hear you and you have every right to be upset, I apologize that we put you in a difficult position with your clients, that’s the last thing anyone wanted.
In terms of the excitement around the feature, I do love the enthusiasm, and while the outcome isn’t what we wanted, I want to make sure we are elevating things that are exciting to all of you and it showcases how amazing the Airtable community is. I appreciate what you all create very much and it was encouraging to see, but I do apologize again for the outcome.
I can’t express the amount of excitement that my users expressed about this update.
Many of my users have been hesitant to commit to adopting the platform entirely.
I have put in a lot of work to craft solutions and demonstrate the integrity of Airtable as a sustainable and scalable solution to them. In four hours, my users and organization went from being incredibly excited to being remarkably disappointed.
On top of this particular occurrence, the communication between Airtable and the broader community about changes, new features, and the platform overall deserves a more comprehensive discussion about best practices and norms.
Any sort of heads-up would be exponentially better than being ambushed.
Nothing is worse than waking up at 6:00 AM, launching Airtable, and realizing that an update has come out of nowhere that tweaks core functionality or how everything looks.
I then have two hours before banks open to brace for the sudden influx of support tickets and frantic questions about changes before team standups. All of that is on top of having to learn everything that changed with the new deployment.
Y’all are seriously about to lose all your consultants and developers. Love you Jordan. As usual not at you and not your fault and I’m sorry you’re the one who has to take the **** for it. But this is bad.