I'm unclear why just using the existing impersonate feature isn't a good fit for this use case?

Fair question. So in my thinking, that feature along with my use-case would require me to logout as the admin, login as the user, logout as the user, log back in as the admin, and repeat the entire process for every user. In other words, extremely time consuming and inconvenient if I wanted to do an audit of all my users (30+, but I imagine many people have even more than that) to ensure they all are only what they should see, for example. Being able to simply have a ‘mode’ I could enter without needing to get temporary passwords for every single user, and basically behave the same way as Facebook’s feature used to - would be pretty awesome. Hopefully that helps clarify a bit.

needing to use the Cloudron method to impersonate a user

I'm unclear why just using the existing impersonate feature isn't a good fit for this use case?

What's the difference between that are what you are proposing? and how is the latter better? thanks!

Not sure this should be part of the dashboard view filters though, but more something part of the user management page, perhaps by adding a button to see their dashboard view.

I agree, I think having that functionality on the Users area instead of on the Dashboard itself would be a good idea.

Once one has a large number of users and groups, things quickly get out of hand mapping multiple overlapping groups, etc.

Not sure this should be part of the dashboard view filters though, but more something part of the user management page, perhaps by adding a button to see their dashboard view.

The purpose of this would be to be proactive before getting reports from users that they don't have access to something they should have, as well as to ensure some users don't have access to more than they need to accidentally too.