Skip to main content

Group Security

Configure remote control approval behavior for devices in a device group.

Updated this week

Introduction

The Security tab controls how remote control sessions are initiated for devices in this group. You can require end-user approval before a technician connects, or allow connection with just a notification.

Settings here are inherited from the parent group or organization by default, and can be forced down to all subgroups.


Remote Control Approval

Navigate to a group's settings (Devices → [group name] → Security).

There are two approval modes:

Notify end-user: The end user receives a notification when a technician connects. No approval is required — the session starts immediately. This is the default inherited from the organization.

Ask for approval: Level sends a request to the end user before the session opens. The end user can approve or deny the connection. If they don't respond, the behavior is set by the fallback dropdown.

Remote Control Approval

Fallback Behavior

When Ask for approval is selected, a dropdown controls what happens if the end user doesn't respond:

  • Connect if the end-user doesn't answer — the session opens after the prompt times out

  • Don't connect if the end-user doesn't answer — the session is blocked if there's no response

Choose based on how your clients expect remote access to be handled.


Inheritance and Overrides

The current setting shows whether it's inherited: "Inherited from [org/group name]" appears beneath the label when this group is using a value from a parent scope.

You can override the inherited setting for this group by selecting a different option and saving.

Forcing Settings to Subgroups

Check Force this selection to all descendant device groups, clearing all overrides before saving to push this group's setting down to all subgroups, overriding any overrides they may have set.

⚠️ WARNING: Forcing settings to descendant groups clears any subgroup-level overrides. This can't be undone — subgroups will need to be reconfigured individually if you want different settings per subgroup afterward.


Saving Changes

After selecting your preferred mode (and fallback if applicable), click Update approval settings.


FAQ

  • What's the difference between "Notify end-user" and "Ask for approval"? With Notify end-user, the technician connects immediately and the end user gets a notification after the fact. With Ask for approval, the end user sees a prompt before the session starts and can approve or deny it.

  • A client wants to approve every remote session. What should I set? Enable Ask for approval and set the fallback to Don't connect if the end-user doesn't answer. This ensures no session opens without explicit end-user consent.

  • Can I set different approval settings for different client groups? Yes. Each group has its own Security tab. Set the top-level group to your preferred default, then override individual subgroups as needed. Don't use the force option if you want per-subgroup control.

  • What does the inherited setting mean? It means this group is using the approval configuration from its parent group or the organization level. Any change here creates a group-level override without affecting other groups.

Did this answer your question?