Welcome to the ConnectWise Control Feature Request Portal
If you do not have an account, click "Sign in/ Sign up" to get started.
Tips
- 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.
Rules
- 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!
Add Option to Share "Host Pass" from Session ToolBar
It would be nice to have the option to share a host past from the toolbar of the session that is in progress. This would allow apps that use the API aka Automate to be able to use host pass.
Right now i have to give users access to both control and automate but the security permissions are different depending on where you log into the platform from.
Unfortunately, this isn't technically possible at this time, as the Host client does not have awareness of the web server.
Manual entry of subnet range search for client network deployer.
Please add the ability to manually enter in a subnet to scan. This is helpful for companies that have multiple sites with multiple VLANS and VPN.
Naming of the records
It would be very helpful if the name of the support account that started the session were included in the file name of the recorded remote maintenance. For example:
ConnectWise_Remote_Session_<Supporter>_<Customer>_<Date>.aviNow when 10 people in a department are working with Control and the files are stored together on a network drive, it's easier to keep the recorded sessions separate.
More Granular 2FA Cookie Control than TrustDeviceExpireDays
I'd like to see better time controls than TrustDeviceExpireDays currently offers.
Use Case: While a lot goes into insure our staff's devices do not get compromised, it could be a matter of time. If an attacker took control of a PC here with saved credentials in the browser, if it's within 1 day, 2FA doesn't prompt.
Sure, you could set TrustDeviceExpireDays to 0, but now I feel I'd be annoying staff with that alone combined with MaxLongestTicketReissueIntervalSeconds.
Ideally, I'd like something like "a few hours" for MaxLongestTicketReissueIntervalSeconds, but maybe 9 hours for TrustDeviceExpireDays (obviously, pretending the word "Days" isn't there). This would force users to re-authenticate after a few hours idle, but not necessarily have to use 2FA, making the assumption with the times I provided above that the user is still working his/her shift.
It's not a perfect idea, but it's an improvement to MaxLongestTicketReissueIntervalSeconds = 7200 and TrustDeviceExpireDays = 0
Ability to Reboot android
Would you be able to add feature to reboot android devices. Currently it doesn’t work using CW client and those controls are useless. This could be handy in many situations.
Notification if thumbprints change
can you give a general alert if thumbprints change for your product when you upgrade, this will assist with antivirus issues flagging your product.
Collapse computer information under the machine list to just the name
We would like to be able to collapse each computer to just it's name under the machine list as it gets really busy. Or have the ability to remove the custom fields under the machine list and just show up on the right pane when the computer is clicked.
sort selection for out of date clients
Please add an option to select all out of date clients to make it easier to update those clients.
Two Cookie Solution - for UsePersistentTicketCookie and TrustDeviceExpireDays
PROBLEM:
The web.config UsePersistentTicketCookie is used badly for BOTH the cookie cache related to staying logged on after closing the browser if forgetting to log off manually (bad for security to leave true, so false is best) as well as used for the new Two-Factor Authentication (2FA) (if you turn the setting to false, now you cannot TRUST a device once you close your browser.
SOLUTION:
a.) Leave the web.config TrustDeviceExpireDays as is, but make it write a 2nd unique cookie for this 2FA, and of course honoring '0' as = false as in not trusting.
b.) Also, have it hide the checkbox if it detects the cookie at '0' as it is odd to have it still show.
c.) Finally, the existing UsePersistentTicketCookie keep as is, but ensure it is a unique cookie ONLY for persistence in staying logged in or not after the browser closes
SUMMARY:
These security measures are distinctly different in their context and application and need to give people the ability to customize either and not have the other one break.
Customer support service by UserEcho