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!
Older graphics cards restrict screen resolution. This is not a problem with the Microsoft Terminal Services client which uses a virtual driver and can display much higher resolutions.
this might already be in the works but did not see it. It would be nice to be able to open up the devices C drive without connecting to the device. to copy and paste files in the back ground.
When you connect to a server the screen resolution can be quite small and there is no way to change the default window size, having the ability to change or set a default connection resolution size or control it in the session would be very helpful, it is very frustrating when you are viewing a sever at 800x600 when you have 1920 x 1080 monitor.
With LetEncrypt now in production It will be an ansome feature if ScreenConnect woukd support it strait at install.
you could offert ssl support out of the box for all client raising the security of your application and reducing the effort for end user to set it up.
We've always liked to be transparent, so we'll try to be better about adding a brief note when we close issues with a high number of votes in the future.
As a product feature, there wasn't a clean way to implement this specific ask. We discussed it multiple times and determined it wasn't a good fit. Our conversations led to improvements, like the introduction of the security toolkit which simplifies HTTP-HTTPS redirect, but a Let's Encrypt integration would have been very hard to maintain and a hack at best.
When feature requests like this come up, we tend to leave them open hoping that advances by the vendors, new tech, and sometimes team bandwidth will allow for them to be completed in the future. We perform internal check ins on most of these issues every 3 to 6 months, but sometimes issues get cut to make way for higher priorities.
Recently, we've prioritized advances in the performance of the session manager, relay, and the router to allow for better performance and scalability. We've also been looking at long time asks that will make the product more human for users, so they discover some of the power user features inside of the product. This of course is outside of the work to stay vigilant in our security posture and squash bugs.
Thank you all for your feedback, it is heard and appreciated.
Senior Product Manager
Be able to apply App.Config files or settings based on the Session Group(s) a computer is in.
make the commands tab a full-interactive PowerShell
would like to send multi-line commands
Partner would like an additional field added to the General tab of the guest machine on the Host page that displays the local IP address of the machine (in addition to the current Network IP address that pulls from the inbound traffic).
Currently if a guest wants to remove a host from a session, they will right click the tray icon and end the session.
When a host joins a access session, there is no way of kicking them besides just stopping the services or uninstalling the agent. Feature request is for the ability to kick a host from a session without removing the agent.
We would like to have the option to add a password to protect the screen connect client from being uninstalled by users with local admin privileges. I have found that when the client is installed from labtech, users don't recognize it and tend to remove it. This causes problems with the labtech SC plugin.
This is a feature that we will not implement for a few reasons:
- OS settings can be applied to prevent users from uninstalling software
- Having a password baked into the agent to prevent uninstall could be used maliciously
- A scammer could essentially prevent an agent from being uninstalled on an unsuspecting victim of fraud
- A legitimate agent could be left behind if the end user no longer wishes to receive service and the service provider does not uninstall the software as part of an offboarding process.
add the ability to audit login failures/successes for logging in to the web interface
Customer support service by UserEcho