TLDR I think I underestimated the scope of your ambition for decluttering(!) and hiding/showing views using rules based on group membership might be the least worst option if we were to develop it.
Unfortunately, I don’t think it’s coming any time soon, so maybe Personal → Favorites is the way to go.
The long version …
Thanks for all the extra info.
Having looked at the diagram, and read all your comments, I can understand why you are lobbying for view-level permissions, although I don’t know if any solution that we would be able to come up with (given enough time and resources) would necessarily make view management a totally pain-free experience.
When I think about designing a schema and sidebar to suit users, I often think in terms of a Karnaugh map whereby I try and determine what are the dimensions which can vary. So a person should see something (or not) based on their membership of one or more groups. In a simple setting, the dimensions might be ‘dept’ and ‘role’, i.e. a user gets to see stuff by virtue of belonging to specific dept or having a particular role.
In your setup, it seems like the problem is way too multi-dimensional. I can’t make a rule about what a Orchid Team Lead can see, because there is no commonality between these leads (as discussed in point 3 above). It’s almost as though there needs to be a dimension for every possible user role.
Now, I understand why that might (logically) lead you to think, “well, we can flip the problem on its head, and simply control per view instead of per user” which does in fact makes sense when there are basically as many distinct roles as there are distinct views.
However, assuming we did introduce ‘granular view level access’ as you describe (even a ‘simple’ version) I think you might find that the pain of administering them (working out who to add/remove) might still make it a bit unpleasant.
Also, I would fear that us solving for your use case (‘hiding for decluttering purposes’) might result in confusion for other users, who come to us saying “I hid this view of Tasks from person X, but I just found out that they can see all the Tasks after all”.
There isn’t a universal understanding of what view hiding should imply, and we’d hate to deliver something that delights a subset of users but frustrates a different subset of users.
Plus, I also don’t know how easy or hard it would actually be from a technical point of view, even if it were ‘just a UI-level’ solution.
Having said all that though, I wonder whether you could reach a slightly different goal by developing all the necessary views in the main sidebar (maybe with spaces per team or whatever suits) and then provide some guidance/training material to help your fellow users understand how they can achieve a less cluttered sidebar through the use of favorites in the Personal sidebar section.
Also, we have just rolled out support for folders in the favourites section which might make this option a bit more appealing.