I would like the ability when a host connects to a guest with multiple monitors to have a separate window opened for each monitor automatically as part of a user/guest preference. Perhaps even memory of last window positions and size on the host side for each monitor... ie guest monitor 1 always goes here, guest monitor 2 always goes here. The thought being if the host has >= monitors as the guest you could have a better experience.

The majority of our clients have multiple monitors and it's time consuming to manually split them out to individual windows manually, and the default "all-up" view results in an unusable experience 90% of the time... more so when they have three monitors.

Partner is requesting the ability to encapsulate all relay traffic in SSL, because occasionally, advanced network devices doing SSL packet inspection over port 443 will drop SC Relay traffic as it doesn't recognize the type of traffic. Partner understands that the relay is already encrypted with AES256.

CW#7833261

Feature: Add an audible sound notification and 'toaster' pop-up notification in browser when a chat message is received while logged into the ScreenConnect host user interface.

Currently, a sound indicating a received chat message is played only when an active support session window is open.

No sound or notification pop up is displayed or made when a chat message is received when logged into the host interface. Only a small green dot is displayed to indicate a received chat message. It is very easy to miss a received chat message without having a support session open to a given user.

i want to have ability to install only one printer on remote computer. right now all my 15 printer shows up on remote computer and they stays there even when i am disconnect from them. and one of them make itself as default.

Partner requests for a public facing road-map to view what SC is working on.

add a de-bugging mode to the client to capture connection information and the last error messages that appear on the client side when activated.

Partner request for the option to use TouchID for iOS devices to log into the SC app.

I have clients that use the remote printing feature of ScreenConnect daily, but after updating to v19.0, remote printing now needs to be toggled manually each time the host connects. I would like it if once remote printing is enabled then it stays active even after the host disconnects, unless disabled manually.

Example: Say you have a server that multiple users remote into. Currently you can assist them by opening an access session to the server, and then changing the logon session from the [serveradmin account] RDP session to the [user that needs help] rdp session. What I'm suggesting (especially as I can see direct benefit at least in my own environment) is to have an option for access sessions to open directly to a specific logon session. IE, rather than having one of my techs open an access session, then select a logon session, instead have them see multiple access sessions for each user, which automatically opens into that user's logon session.

This would be helpful for a variety of connectwise environments:

-It would be useful for those who charge clients a monthly fee based on how many users they support. It's easy to track supporting X number of users when you have X number of computers with access agents installed, but can be difficult if you have an unknown number of users that remote into a central server. If you were able to create access session groups based on user logon sessions, it would be easier to track active users. Because it's one thing to see that logon sessions on the server exist for whatever number of users, but it's another to be able to see things like 'this access session for User7's server session hasn't been logged into by a tech in months'

-It would be useful for those who assign specific users to specific Technicians (EG, companies that have tech1 assist users1-30, tech2 assist users 30-60, etc), as you could just give each tech permissions to the sessions for each user's logon session, instead of the entire server.

-It would be useful in helping stay organized with companies/clients that have large RDS environments, where you may have 30-40 users remoted into a given server. Instead of needing to go through a massive dropdown from the screenconnect client, you could leverage filters and groups through the web portal.

Those are just the examples that spring to mind right away, in addition to my own admittedly niche needs, just to demonstrate that a lot of people could benefit from this feature. 

Have the option to only allow authentication through SAML once it's integrated.