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!
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.
Background: Control 6.5 imposes a signature validation scheme to ensure the integrity of the Connect install (per this post). This is a net good for most of the community base. For the rest of us it's more trouble than it's worth.
Request: We need the ability to either whitelist custom extensions from validation or disable the signature validation scheme entirely.
Reasoning: I've developed quite a few extensions in an on-premise Control installation to automate significant portions of my business. I'm not willing to share some of this code since it exposes the inner workings of my business, sometimes usernames and passwords, trigger URLs, and plenty of other information that would be useless for the rest of the world, but could increase the risk of my own business data should it be shared with a third party -- even ConnectWise. Microsoft, Google and Adobe have each been hacked in the past, so it's safe to assume that anything I share with CW will eventually be exposed as well.
The hosted developer instance option requires me to share business logic and requires significant rewrites to the code for each of my extensions to be able to prevent business information exposure. Furthermore, as far as I can tell, some of the functionality can not be rewritten in a way that prevents this exposure.
I've submitted an extension to CW in the past and it took weeks to have it approved. It took weeks to be approved for a developer instance. I can only imagine initial approval of each of my extensions to be able to use them in my own on-premise install will take weeks as well, and even minor updates to my extension (such as cosmetic changes or field formatting) will likely take weeks to be approved as well.
On-premise users require the ability to continue to use and develop our extensions without exposure to ConnectWise. Please enable us to whitelist our custom extensions within the web.config so we can maintain the integrity of our own installations and source code.
Ideally we could customize hide/display what information is displayed under the computer name in the middle viewing area. These view settings should be independent of the side information panel. This is particularly relevant when enabling custom properties to be displayed, as they show under the name and it congests the view.
We would love here to have a feature called ‘Recent Connected Sessions’ is there a way to do this please?
Not only would it make checking up on the team easier but have a tenancy as large as ours sometimes when you accidently close a session or need to get back on quickly it takes a while to find it.
In the Access view, the pane on the right with the thumbnail should be combined with the general tab that has IP and login information. Like older versions of the software.
when looking at my list of machines on the access page, if the session is expired there is no indication. When you then try to initiate a remote control session it fails silently.
The "micro mouse" used for control in the app is an ongoing daily frustration. Every single time. Multiple times a day.
The scroll wheel in particular is really horrible. It scrolls things when I don't want it to. It doesn't scroll when I do. It's damn phone. Who the heck thought a super tiny mouse was an appropriate way to do remote control?
Please take a look at Splashtop. They do it "right". They have a mouse mode that works better than CWC. Better, they have a touch pad mode that works quite well. Which is probably why most laptop manufacturer's use it.
Please please please fix the CWC mobile experience.
When connecting to a client's mobile device using the ScreenConnect App, it pretty much has no useful functionality. As an MSP, clients call in requesting help setting up setting up their emails. Sometimes we end up sending someone onsite because there is no way for us to see what the end user is doing.
It would be great to have access to the mobile desktop to make these setup easier. Even some sort of limited or view only access would be helpful than no access.
If you're using an Android device to connect to a mobile device or if your end user/guest has an Android device, please make sure to install the ConnectWise Control App. It is the only app still receiving updates.
If you or your guest has that app installed and you're still having trouble I suggest you reach out to our Support team so they can help you.
You should be able to view an iOS device, but you will not be able to control it.
For example currently running whoami returns the following:
I would like an option to run the command as the current end user, so instead whoami would display:
There are many applications that assume you are running from the current end user.
Thanks for the help with this!
Customer support service by UserEcho