Your comments

It doesn't matter the case. We have 5 roles and even that is too many to have to handle the above task. It is backward from any other system. If you were using AD and put a new folder on a network... your members wouldn't just have access to it unless you set the access to everyone. It would require to you add the roles/members you wanted to have access to it. But your system automatically gives everyone access without allowing the admin to restrict the access to roles without having to open each role one by one to adjust their rights individually.

I gave an example above that was pretty clear but I will try to give another example. Your system is set up so that a new session group shows up for all roles. If I set up a 'Support' role and a 'Systems Admin' role and I create a session group for only the systems that the Systems Admin should see I have to go into all existing roles and any new roles and uncheck the ability to see that session group. This might not be an issue for one or two roles but if you have many session groups and many roles this becomes a large process each time you add a new role or session group.

It makes a lot more sense, in my opinion, to have session groups hidden from all roles that don't have explicit access. When a session group is created it should ask what roles you want to see it and when a new role is to create it should ask what session groups you want them to be able to see. On any role-based service, I have used besides this one grouping, folders, access, etc isn't granted by default... it has to be given.

Another example, if an employee wants access to their systems but doesn't want any of the other staff to have access to their system the admin would have to create a session group for those computers and instead of granting access to only that employees account or role they would have to go into every existing role and hide the access to that session group. Let's say you had 30 different roles in your business, to hide that one session group you would have to open and edit 29 different roles just to hide access to a session group vs opening one role and giving access to that session group.

Short and sweet, there is no easy way to create a session that only one role can see without going in and removing access from every other role in your system. Worse off, if you create a session group that should only be visible to one role, add a new role, and you forget to remove the access to that session group for that new role you now have a role that can, out of the box, see a session group it shouldn't. This is time-consuming, problematic and the opposite of how every other role restricted system works.

This is a really important feature for my work. I deal with people with 2 to 3 monitors and I am constantly having to stop what I am doing, grab my mouse, move up to the monitor button, wait for it to open, then click the monitor I want. It seems like a simple task but it really gets in the way of my job on a daily basis.

Its all well and good but that can be a later update. It should be easy for CWC to default to only opening the default screen on the guest system. Why would we ever need to see all the screens by default? In 99% of the cases, I open the guest session and have to go up and tell the system to switch to a single monitor. I don't care about the position of the window but when changing from 2 or 3 screens down to one the window doesn't resize to the full size of my screen. I have a larger screen with plenty of real estate but the window of the guests desktop stays small in the middle of my screen which means I either need to make it full screen or drag the edges till it uses more space on my screen.

How is this still pending review after two years! Many of my clients have two monitors and Control always opens with both monitors. This default function is worthless in my opinion. When the program opens both monitors both are too small to do anything, the Control program sizes the window to my desktop... but it is sized for two monitors so when I change it to a single monitor it stays small, making it equally useless until you either make the window fullscreen or waste time dragging and sizing the window to my screen.

The fact that this is still being considered is irritating. There are duplicate requests from people wanting this feature, multiple replies to said requests and plenty of upvotes... We need this to function in our jobs without having to stop and switch to a single monitor and resize the window each time. I don't care if it is a setting you can turn on or just the default way the program should function but I have used plenty of other remote support apps and not one of them opens to multiple screens as the default option... because no one uses it that way!