TotalHealRemoteLink

How it works

1. RequestA technician opens a session from the console with a reason.
2. ApproveOptionally a second person approves; the requester never approves their own session.
3. ConsentThe person at the device accepts in a native dialog; no answer in 60 seconds declines.
4. WorkView or control, with an on-screen indicator and End session always visible.
5. SealThe recording is sealed and encrypted, with time-limited playback for auditors.

Reference architecture

Key capabilities

• View or control from the browserScreen view or full control of an enrolled Mac or Windows PC from the web console.
• Consent on the deviceA native consent dialog — always on personal devices, on corporate devices unless policy turns it off. No answer in 60 seconds declines.
• Optional second approverA second person must approve; the requester can never approve their own session.
• Sealed, encrypted recordingsServer-side recording, sealed with SHA-256 and encrypted at rest with a per-organisation key you can rotate, with chain of custody and time-limited playback links.
• Always visible to the personAn on-screen indicator with “End session” for the whole session; keystrokes are never injected into password fields.
• Files and clipboard, off by defaultFile transfer both ways is consented separately, size and type limited, scanned before it is written and encrypted at rest. Clipboard sharing is off by default.
• Remote Shell for serversLinux servers (and desktops if enabled): approval for production and root, risky-command blocking, recordings with integrity check and command search.
• Limits you setMaximum duration 5–480 minutes, idle timeout 1–120 minutes, one live screen session per device.
• Finds other remote toolsDetects other remote tools and OS sharing services on the device and offers to turn them off. Every step lands in the hash-chained audit.

In the console

Deployment options

System requirements

Technical specifications