Splashtop offers unattended remote access and by default, the user is not prompted to accept or reject the connection.

Splashtop Security Settings

To request permission to connect remotely to an end user's device via Splashtop:

To switch to attended settings, the end user can enable this security option directly from the Splashtop Streamer app on the endpoint machine.

1. Open the Splashtop Streamer and go to the Security tab > Request permission to connect.

2. Select Reject connection after request expires (At login screen, reject automatically).

Once this security setting is enabled, the end user will see the following prompt when the technician initiates a remote connection from Atera.

Atera's Shared Script Library

To request permission to connect remotely to an end user's device via Atera's Shared Script Library:

To switch to attended settings, the technician can enable this security option via Atera's Shared Script Library.

1. From Devices, on the side panel, click the Manage dropdown menu on the device you'd like to connect to.

2. Then click Run Script. The Run Script window appears. 

3. From the Shared Script Library tab, locate the Request Permission to Connect (+ Auto Allow after 30 seconds) script. 

4. Click Clone to copy the script over to the My Scripts tab.

5. From the My Scripts tab, locate the newly cloned script and click Run.

Once this security setting is enabled, the end user will see the following prompt when the technician initiates a remote connection from Atera.

Note: You can add the script to an IT Automation Profile and execute it automatically on newly installed agents by checking the checkbox next to Run the profile on newly installed agents.

Check out this video that explains how to set up Splashtop to request permission from the user when connecting remotely. For more information on scripts, see Run a Script and Create or Upload Scripts

Scripting

"Reject connection after request expires" script:

You can also enable this security setting remotely by tweaking a few registry keys via scripting.

The registry key has four possible values (all these can be used locally or via Atera):

0 - Disabled
1 - Reject connection after request expires (At login screen, reject automatically) 
2 - Accept connection after request expires
3 - Reject connection after request expires (At login screen, allow automatically)

The command:

wmic os get osarchitecture | find "64-bit" && reg add "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Splashtop Inc.\Splashtop Remote Server" /v EnableSharePUC /t REG_DWORD /d X /f || reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Splashtop Inc.\Splashtop Remote Server" /v EnableSharePUC /t REG_DWORD /d X /f 
net stop "SplashtopRemoteService" 
net start "SplashtopRemoteService"

Please ensure to change the value of the X variable.