Welcome to the ConnectWise Control Feature Request Portal
If you do not have an account, click "Sign in/ Sign up" to get started.
- Search for an existing improvement or feature request before adding your own. This helps us prevent duplicate entries and track all suggestions.
- If you find a matching request, give it a thumbs up and throw in a comment.
- If you can't find a request for an item you need, create your own request. Provide as many details as you can, especially regarding possible use cases.
- No spam, advertising, or self-promotion.
- No offensive posts, links, or images.
- Only one request per post.
- Administrators have the ability to moderate the forums, including editing, deleting, and moving posts. Posts may be deleted for any reason, with or without notification.
Thank you for sharing your thoughts with us!
It would be very useful to be proactively notified when a new version of ConnectWise Control is released via RSS Feed or via an email as opposed to having to periodically check the "Version Check" page in the Admin Status section.
We recently moved to ConnectWise for the Access feature that it included. One feature that seems to be missing over the product we moved away from (LogMeIn Rescue) is password storage for "unattended sessions".
In an unattended session, the user grants access to their machine by entering their username and password which is stored for the duration of the unattended session. Access offers better accessibility to our end user machines, but when I am performing a Windows build upgrade, it is easier to sign in as the user so the profile provisioning process completes before the user goes to use their machine the next day.
The current limitation by Access is that we can capture the credentials and push them UNTIL the computer is rebooted for the build upgrade (e.g. Windows 10 22H2). After the reboot is completed, the credentials will no longer push. If this feature could be improved by allowing for longer storage (such as for maintenance), it would be much appreciated.
Is than an estimated release date for the Mac M1 client? The current client installs sucessfully, but never registers in the control panel.
All, I wanted to give an update on this. We have finished scoping out the work required and will soon be scheduling the work. I can't give a firm date on when this will be available yet, but will update when the work is nearing completion.
When chat window opens, it is on top of all others and must be acknowledged (clicked) before it goes behind.
Currently, when the chat window opens, it opens behind whatever the active window is and, with my clients at least, is often ignored until they finally close what they were doing.
I would like it if, when the chat window opened, it opened on top just like a regular new window does - and most require that they are clicked before they can be pushed behind others. This would force the client to acknowledge the window is there. This way, if they choose to ignore me, they go to the back of the queue and I can move on to another client.
We are looking for when a SC session ends or we exit, that the Windows session also get logged off. There are too many times where a SC session disconnects, and the next day someone goes to log into the server, everything is left off where the previous tech was. We need this to be clear when a user logs into the system.
Add the ability to have a shared clipboard by default and toggle off as needed, instead of set to off by default.
You can change the default behavior using the Advanced Configuration Editor extension:
The specific setting to change is described in that article, but a more visual document is available here:
Clipboard sharing during a remote session - ConnectWise
Please add "Installed Software Report" in Report Manager option!
On systemd systems, generate a service unit file and use restart option to ensure service is recovered from crash
On Linux systems running systemd currently no unit file is generated for the guest service thus if the service crashes the init system will not restart it. This is simple to do, and offers a simple way to automate service recovery which is important given ScreenConnect (Control if you must) might be the only way to access that system.
Also, the service is not started automatically after install via .sh file and it should be. No one installs ScreenConnect and doesn't want it running.
Customer support service by UserEcho