Remote support
In-browser remote desktop for endpoints you manage
Connect to enrolled devices with in-app remote desktop — screen, input, file transfer, clipboard and multi-monitor — with MeshCentral integration and per-organization isolation.
Backed by app modules
- Technology
- In-app remote desktop viewer
- In session
- File transfer and clipboard
- Session features
- Multi-monitor and session recording
- Isolation
- Per-organization Mesh isolation
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
How it works
Enrol the device
Remote access runs against a device already enrolled in device management, so the same agent that reports the device also carries the remote session. No separate remote tool has to be installed on the endpoint.
Open a session over one socket
The operator browser and the device agent join the same per-device WebSocket relay. The agent authenticates with a hashed device token, and the viewer is authorized only if the operator organization owns that device, keeping sessions isolated per tenant.
Control the endpoint
The agent streams the screen as changed tiles with periodic keyframes while the viewer injects mouse and keyboard input. The protocol also carries multi-monitor switching, two-way clipboard, a live chat channel and chunked file transfer over the same connection.
Require consent and record
A remote session is stored as an audit record with a one-time session password and a consent flag, and the session can be recorded. Recordings are saved as timestamped frame logs that replay onto a canvas at the original cadence for later review.
Already live in the product
Running in production today: in-app remote desktop with MeshCentral integration, built into device management. Protected app route: /mdm-dashboard
A worked example
Say an MSP technician supports 700 managed endpoints across a dozen client tenants, and a finance client reports a broken VPN profile on a director's laptop. The technician opens a native remote session from the browser; the agent joins the per-device relay with its hashed token, and the viewer is admitted only because that tenant owns the device. The director approves the consent prompt, a one-time session password guards the connection, and recording is switched on. The fix takes minutes — new config pasted through the synced clipboard, an installer dropped over the same socket — and the audit record plus frame-by-frame replay are there if the client ever asks who connected and why.
What teams can do here
- Step 1
- Enrol a device
- Step 2
- Start a remote session
- Step 3
- Assist the user live
- Step 4
- End session with audit trail
Frequently asked questions
See also: Guide: best remote desktop software · Guide: what is RMM? · RMM & endpoint management · Mobile device management · MDM overview
Fix any managed endpoint without leaving the browser
Consent-gated, recorded sessions over one WebSocket — screen, input, clipboard, chat and file transfer on the same agent that already manages the device.
