Skip to content
Browse all help topics

Permission profiles, “ask before connecting” and the connection manager

Control what sessions may do, when the person at the computer must approve, and how they can restrict or end a session while it runs.

On this page

Three layers of control

1. Permission profile
What a session may do (keyboard, mouse, files, terminal…). Set by admins; enforced by the agent on the computer.
2. Approval
Whether the person at the computer must accept first, and whether they grant full control or view only.
3. Connection manager
While connected, the person at the computer can switch off individual permissions or disconnect you.

1. Permission profiles

  1. Go to Permission profiles (owners and admins) → New profile.
  2. Name it (e.g. “View and chat”), untick what it may not do, and switch on Default for every session your team starts if wanted. Save.
  3. To use a different profile for one computer, add an unattended password with that profile on the device page.

In a session, anything blocked appears in a Limited: … badge and its buttons are greyed out. The full list of permissions is on Permission profiles.

2. Asking before connecting

SituationIs the person asked?
Connect by ID + access code, “Ask me before someone connects” ON (default)Yes — Allow full control / View only / Decline.
Connect by ID + access code, “Ask me before someone connects” OFFNo — anyone with the ID and code gets full control straight away.
Connect by ID + unattended passwordNo — the password’s profile applies.
Your own workspace’s devices, policy “Only connect-by-ID + code (default)”No.
Your own devices, policy “Every session, including your own devices”Yes, when someone is signed in at the computer; with nobody signed in the session goes ahead.

The switch lives in the desktop app — on the sign-in screen under THIS DEVICE, and in Settings → This computer. The policy lives in Security Policy → Ask the person at the computer to accept; Who may connect by ID + code can further limit code connections to signed-in users or an allow-list.

Careful: With the switch off, the 6-digit access code is the only thing protecting the computer. Keep it private, and remember it changes whenever the agent restarts.

If the person picks View only your session shows View only (chosen at the computer) and your input is ignored. If they decline or don’t answer, you’re told: “The person at the computer declined” / “Nobody at the computer answered the request”.

3. The connection manager (on the controlled computer)

When the person at the computer accepts a connect-by-ID session, a page opens on their computer: Who is connected to this computer — “You stay in control: turn off anything you don't want them to do, or disconnect them.”

  • Each connection shows who it is and how long they’ve been connected.
  • A switch per permission (keyboard, mouse, clipboard, files…). They can only take permissions away, never add more than the profile allowed.
  • Disconnect ends that session at once; the technician is told the person at the computer disconnected them.

The page is served only to that computer itself, and nothing on it leaves the machine. When nobody is connected it says “Nobody is connected now. You can close this tab.”

Making sessions visible

Coloured frame on the remote screen during a session (Security Policy) draws a border on the controlled screen; it disappears within a second of the session ending.

Related help