The use of views is obviously a crucial and powerful aspect to airtable but it can very quickly get bloated, especially when a base is being shared amongst a team.
My first thought is to have “private views” or “user view”, which I think reflects airtable’s goal of creating a tool that allows users to define their own tool. Within a certain table I may want to save multiple views that are really only relevant to what I want to see, and there’s no need to a) clutter up the views list for everybody and b) allow anyone else to see or edit these views.
This would also solve some of the requests regarding granular permissions for views.
For the public views, I still think it would be great to have a way to save the settings of a view so multiple people can use the view without changing it. For instance, if there is a view that just shows all the records, if somebody on the team starts filtering things, and doesn’t remove the filters, the next person who selects that view will see all the filters. On our team, we’ve been making different views for each user, both so our personal selections don’t effect others, and so we can look and edit the same data at the same time without affecting other users views. However, it would be great to be able to “revert” to a set saved state for a specific view. I find we don’t treat each view as a static state, but a starting off point.
I know some of these issues have been discussed on the forum, but I think these types of solutions, “user views” and “revert” could solve a lot of the problems we’ve been having.
Another level of organization for the views would be to have sub-folders for views. Just something else to think about!
