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.
It would be nice for the guest to have a button to disconnect the remote session, similar to have Automate's VNC disconnect now.
Currently, the only way to end a session is through the Control server.
Add the ability for a remotely accessed computer user to end the session.
In other words, if I am accessing a remote user's unattended computer, and they sit down in front of it and want to use it, there is no way for them to end my session short of uninstalling the agent or disabling the service--both unnecessarily cumbersome ways to simply be able to kick a remote user off their machine temporarily! Most other RMM services have this feature, seems strange for Screenconnect to lack such a basic feature. Thanks!
We have users that work with confidential data and need to be able to disconnect the support engineer when working with this data. They need to be able to issue a disconnect and have that revoke the permission token that would allow the engineer to reconnect without the user granting permission again.
Can an option be added for the end-user to have a disconnect option? We use Access and push the Agent via SCCM. An option to right-click the screen connect icon and have a Disconnect or Disconnect Remote User - something along these lines as an extra security measure.
Thanks!
This has been implemented as 'Require My Consent' here:
Enable a guest to require consent - ConnectWise
It enables a Guest to right click on the system tray icon to require consent, and in the case where a host is already connected, selecting the option will forcibly remove the Host from the sessions.
This is a need. Original submission for this was 3 years ago and it is pending review. What is the timeline for review?
There are many reasons why the host may not have disconnected, the client has very little recourse to drop the connection, Task manager to kill the session is not acceptable method for a client to disconnect.
For us it is a requirement as well, also based on german labor and dataprotection laws.Please add the functionality for the end-user to disconnect a technician from his or her computer.
Our EU company is also now in this as well..Previous because our customers were outside EU it wasnt a concern with permission but not the case now.. Please can this be made a feature? It doesnt need to END the Access Session but just be able to kick off the technician.
Maybe it helps others here. We have for now declared it as a security feature, since it prevents users from kicking out a technician while the technician has for example an admin-prompt open over remote.
If the user were to kick them out in that time, they could do whatever they want and get access to sensitive information or systems. Without that option its in the responsibility of the technician.
Nevertheless it would be great to have the option to enable it upon request.
The option to close the control session is only enabled for support sessions. With the GDPR it is a requirement for the users to be in full control of their data. This includes remote sessions and our customers need the option to have their end users cancel out of an access session as well.