MultiTenancy

Hi there! First of all, let me be totally grateful for your dedication on this project. It means a lot to me who is an "opensourceaholic". Seriously. God bless your life, family, friends and knowledge.

Is your feature request related to a problem? Please describe.
I always wondered if I could use one server to fit all my remote needs in the remote support world. Found the solution a while ago but it wasn't how I wanted it to be. My goal is to have attended and unattended access on the same organization.

Describe the solution you'd like
I would like to be able to set attended and unattended access on the device group (and if possible, device subgroups) level. Picture it like this: I have IT outsourcing contracts with customers that has servers and desktops. Let's name this company "Star". So I create a device group called Star and two subgroups named Servers and Clients. I would like to use the resident agent on every machine on the company. Machines that are on the Servers device subgroup will have unattended access and machines that are on the Clients device subgroup will have attended access. That way I will only use the portable agent if I need to remote support a client that has no contract with me.

Describe alternatives you've considered
I tried two alternatives and sticked with the second one since the first didn't work as I expected.

First: I increased the organization number so I could self register again. The first problem I ran into was that a user can't coexist on separate organizations of the same servers. But that was ok. I registered with a gmail account and got in to my new and fresh tenant. Everything was going fine until I tried to change the branding. I kept receiving and error. And funny fact is that my new tenant did not get the branding from the default organization. As it wouldn't work well, I jumped to a second alternative.

Second: I build another docker from scratch and did all configurations the exact same as my first working Remotely Container. Now I use one for the servers and the other for the clients. The only difference is the URL used to reach one or the other.

One advice I give is to use different Authenticator App for each server if you're gonna use the same e-mail to log in on both (if you use 2FA).

Additional context
Now it suits my needs as it is and works as a charm for me. But I can't deny that it would be great if I could do all this on the same organization.

BTW, I'm using the latest version on docker in an Ubuntu 20.xx LXC Container on Proxmox 7.1 and 7.4. Both cases with Cloudflares Zero Trust mechanisms.

Start by examining how organizations, device groups, and attended versus unattended access are represented in the project. The requested outcome is access behavior configurable at device-group and possibly subgroup level, with servers using unattended access and clients using attended access; the issue names no files or tests to begin with.