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!
Creating a rule/group that removes/uninstalls Access agents if they haven't been online for more than one year.
Would like to customize the temp location where "As of version 5.5, when you run a tool from the shared toolbox, the tool will be downloaded to a temporary folder on the guests machine. When the session has ended, ScreenConnect attempts to delete the downloaded tool from the temporary folder."
I would like to request that you add-on the ability to add a second login for the cloud admin accounts in future iterations of your program. Trying to purchase an extra license was quite an ordeal. It took a week to get ahold of anyone in your company and then someone explained that the only way that is conceptually possible to add any kind of license is through the cloud portal, but you guys don't allow companies to have more than one user registered for access to it. I was kind stuck in between a rock and a hard place because of this today. I just think that this would make user administration easier across the board for everyone. Companies would have more autonomous control over their own accounts. Because of this they theoretically wouldn't have to open as many tickets with you guys for either question like I had or needing to gain access to the said account because there is only one and that person is gone or something. Food for thought hopefully anyway.
This is a must, I guess, for everyone.
It's important when you open a session, to see Computer's name on the top left corner.
But as important as this, is to have also:
* Organization (field) where you put particular info for this session)
* User (field)
I have to work with more than one session at a time very often.
So It's hard to relate by Computer Name, instead to see to whom each session (pc) belongs (user) when I switch between those.
I did ask for this suggestion already, but I'd like to see it in this new release, please !
Partner is looking for a means to be able to use smart cards through a session to support smart card requirements for admin functions on remote systems. Notes that RDP supports a pass through device so local smart card is presented through the RDP session to the remote system for Authentication.
As a user, I want to be automatically logged in after I complete the last step of a mult-factor authentication process so that I have fewer steps and clicks before I am logged in.
Currently, after completing the final MFA step, CWC still sits at the login screen and we have to click the Login button to actually get into the system. It's a relatively small thing but it helps when we have a relatively short login timeout.
Would like the ability to set Default Clipboard Sharing Settings based on if the machine is a Server or if it is a Workstation.
Options would be Default to On, Off or Disabled
Servers - Share Clipboard - Defaults to On
Workstations - Share Clipboard - Disabled
If this functionality already exists can you point me in the right direction to set it up?
Having a feature to automatically clear the guests clipboard when disconnecting from a session. Having a shared clipboard can be very helpful in some circumstances. With clipboard history in Windows 10, this makes
While disabling Clipboard Sharing and using Send Clipboard Keystrokes achieves the same results, it would be nice to know the clipboard is cleared when disconnecting.
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.
Customer support service by UserEcho