Add previous world visitors to the permissions tab under session settings

Is your feature request related to a problem? Please describe.

I had an issue with a user in the world today who was leaving and coming back while causing problems. I was AFK so I didn't see this happen first hand. I didn't catch their username while in the world with them. Personally I wanted to ban that user from my hosted sessions but without a name I couldn't do that. I would have also loved if they could have had their permissions changed to spectator, but for that to happen they have to be in the world as far as I'm aware.

I really wish there was a way for me as a session owner or just someone with moderator privilege to be able to have a list of users that have joined the world even if they've left so that I could set their permissions or even ban them if they choose to return.

Describe the solution you'd like

I would love to see the permissions tab of the session menu changed to include a section where any users that have visited are listed, allowing action without waiting for the user to return.
very quick lil mockup

Describe alternatives you've considered

third part user join leave loggers like the one used in CJ - Being a object in the world a malicious actor could edit itto remove themselves, and this doesn't allow a mod to change permissions Checking the undo manager - shows a user ID, not username, so you can't find that user easially using the contacts tab

Additional Context

while I understand this can make the UI more cluttered (and adjusting the UI is a mess right now), I think this could be a very useful moderation and safety tool to help stem off griefers or other people that might pop back in when you aren't expecting

I'm not sure that this is something we'd be likely to prioritize on the existing interface- it's probably in need of a rework.

There are also some additional features that have some relation to this one, e.g. #1108 - a mechanism to track recently met users, #1121 - setting per-user permissions globally across Resonite, and the hard permission system: #1103 - which would allow more granular control of what can be spawned into the world/how the world could be modified.

In the interim- I'd recommend that you set your default permissions to be a bit more restrictive if you are going to be working in public sessions, e.g. preventing cloud avatars from being loaded by default, and defaulting permissions to spectator in the world.

There are also user-made tools that can help track session joins/leaves which could give you some record of that user's malicious activity which would also be potentially useful in the event you submitted a report about that user to https://moderation.resonite.com/.

Yellow-Dog-Man / Resonite-Issues