Remote Control & Interactive Console

When a user at Acme HQ needs help, an operator opens Remote Console from Endpoints on acme-wks-01, shares the desktop when needed, uses the interactive console, and leaves a session record for the next ticket.

FlowRMM Remote Console is the Cohort 01 path for accountable remote work: start a browser session, take control when you intend to, run a shell or copy a file, and keep a session record the next engineer can read. It is not a claim that every future RMM module ships today.

Open a session on an Acme endpoint

Open Endpoints and find acme-wks-01 (or the Acme Corp endpoint you enrolled).
Choose Remote (or Open Remote from the endpoint drawer).
Confirm Start viewing: the portal does not stream until you engage.
Stay view-only until you are ready; the first intentional click or key arms control.
Use the status ribbon (Connecting → Waiting for frames → View only → Control armed) to know what the session can do.

If frames stall, try Wake before treating the session as failed. Soft reconnects should resume quietly when you return to the tab.

Desktop view and control

Prefer the console desktop when you need to log in, unlock, or help the person at the keyboard.
On Windows, additional RDP sessions may appear in a session picker: mouse and keyboard always go to the desktop you are watching.
Utility UI (Windows-only) is a separate technician surface for tools; it is not a fallback login desktop. It is hidden on macOS and Linux.
One rule: if you can see it in the viewer, your clicks and keystrokes go there.

Interactive console

From the remote workspace, open Console for an interactive shell on the endpoint (Command Prompt / PowerShell on Windows; common shells on macOS/Linux). Use read-only checks first; treat mutating commands like any other operator action that may need approval.

File copy

Use in-session file copy from the console workflow when you need to stage a small file on the endpoint. Prefer the portal path over ad-hoc side channels so the work stays tied to the session.

Clipboard and lock screen tips

Armed sessions can share a session clipboard; view-only sessions do not sync clipboard.
On a Windows lock / sign-in screen, ordinary clicks often do nothing: use Ctrl+Alt+Del from the toolbar, then Type clipboard for long passwords when the field is focused.
If an unlocked mirrored session is available while the console is locked, the portal may land you on the clickable session first; switch back to Console desktop when you need the lock screen.

What Cohort 01 does not promise here

Dense capture-pipeline internals, automated smoke harnesses, and deploy runbooks stay out of this public guide. Judge Remote Console on the operator path above in your environment: OS, desktop session, and permissions all matter.

Related guides

Want hands-on help evaluating Cohort 01? Book a demo or apply for Cohort 01.