0
Closed

Add "Join with user consent prompt" option

GrantG 3 months ago updated by swhite (Product Manager) 3 months ago 3

We don't need the more advanced consent controls, we have permission, this is just to enhance interaction with end users.

If we are responding to a non-realtime user remote support request, we want to give them a few seconds to close sensitive documents they may have open, before we connect, as a courtesy.  
Ideally with a timeout you can configure right there, or a global default timeout.

For example, 5 minutes after they send an email requesting support, instead of a either needing to lookup and contact them, or a sudden "Your computer is being controlled by XXXX", they could get a "XXXX would like to remotely connect to your computer: Allow/Deny [Countdown].

Like the "Remote Control: Prompt for confirmation" option in Teamviewer. 

Then, if they don't respond, we can just use the regular Join option.

Available in Version:

Answer

Answer
Closed

Prompt for consent is the way to do this, you can then configure the timeout for auto-consent if there is either no user at the machine or the request is not acknowledged. 

Prompt guest for consent before connecting to a remote machine - ConnectWise
Automatically grant consent after a countdown - ConnectWise

Automatically grant consent if no user process is running - ConnectWise


 

Answer
Closed

Prompt for consent is the way to do this, you can then configure the timeout for auto-consent if there is either no user at the machine or the request is not acknowledged. 

Prompt guest for consent before connecting to a remote machine - ConnectWise
Automatically grant consent after a countdown - ConnectWise

Automatically grant consent if no user process is running - ConnectWise


 

Thanks for those links, that could get us closer.

For our usage, 90-95% of the time, we don't need to jump through the consent hoop, which is why it would be nice for it to be a separate option when connecting that other 5-10%. 

Same techs, machines and users.  There may be certain machines we would want consent a higher percentage of the time, I will have to review with those users.

Makes sense. Best bet would be to put those machines that do need consent into a session group and then remove the HostSessionWithoutConsent for that session group.