Help

Upcoming database upgrades. Airtable functionality will be reduced for ~15 minutes at 06:00 UTC on Feb. 4 / 10:00 pm PT on Feb. 3. Learn more here

Oops! Editable shared view update

cancel
Showing results for 
Search instead for 
Did you mean: 
Jordan_Scott1
Former Employee

Hi all -

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.

54 Comments