Remote access approval different approval settings.
Need different approval settings for remote access based on the device type. I want my helpdesk technicians to be required to get user approval to work on their system, but my server admins should not need approval to remote into a server since there is no one at the server to allow the access. This could be based on the role in the platform like Admins can skip the request, while technicians are required to get the approval.
Jason Campbell
shared this idea
-
Hi there,
Yes - you can control remote-access approval and behavior per connection type using roles and configuration policies. Here’s the quickest way to set it up.
Role-based access (what a technician is allowed to do):
Admin → Access roles → New role (or edit).
- Remote management: allow access to Workstations, Servers, or both.
- Scripts: allow/deny Run scripts and limit by script categories (e.g., block server-only scripts for endpoint techs).Save → add the relevant technicians to this role (Members tab).
Account-level Splashtop settings (default for the tenant):
- Admin → Settings → Remote access → Splashtop settings.
- Choose attended (end-user approval required) or unattended (no prompt) and set other defaults.
- Save.Per-site/folder override via configuration policy:
- RMM → Configuration policies → New policy (or edit).
- Splashtop section → enable “Override account settings.”
- Set the mode you want for this scope (attended or unattended).
- Assign the policy to a folder/site or specific agents to enforce different rules per group.
- Save and apply.Note: this override currently applies to Windows devices.
Tips
• Use multiple policies (Folder-based/agent-based) if you need different rules for servers vs workstations or by customer/site.
• Pair policy overrides with Access roles to both limit who can connect and how connections behave.KB on the matter: https://support.atera.com/hc/en-us/articles/115001957308-Splashtop-remote-access#ManageSplashtopaccessviaconfigurationpolicyoverrides
