Yes, seems like this has been needed for many different purposes & workflows, and for some time now too. Here’s just one example from my office:
We have a Print Editorial Calendar base (based loosely on an Airtable template), but possessing a huge scope of monthly editorial content throughout a calendar year. For our purposes, this means a couple hundred records—one for each content piece—in our single Print Schedule tab, in addition to a dozen fields linking to each issue, fields setting deadlines, fields for attaching unedited and edited drafts and photos. etc.
Some of this editorial content is being collected and edited by a couple of interns, who we are trying to reserve as much superfluous information from as we can—anything that doesn’t relate to their designated assignment. Moreover, there are so many variables due to such a large and content-heavy base that we want to minimize any unintended mistakes, which we’ve already had before. But that being said, they need to be able to make edits or re-attach updated drafts or make notes for some of the records—a few out of the couple hundred in that table. (Even some limited editing usage — such as just the ability for them to only input attachments into attachment fields — would be immensely helpful.) We house quite a bit of proprietary information for upcoming content in that single base, which works for us in every way EXCEPT for this issue with limited collaboration/editing.