Concorbit HelpAll guides →

Remote Access

Remote access

concorbit RMM provides browser-based remote desktop and terminal access to any online device. No client software is needed on the operator's machine.

Remote access requires a paid plan.

Remote desktop

Click Remote on any device to open a live desktop view. The connection uses WebRTC for low-latency video and input.

  • Full mouse and keyboard control

  • Multi-monitor support (select which screen to view)

  • Clipboard sharing

  • Works through firewalls (peer-to-peer when possible, relayed when not)

  • All sessions are logged in the device timeline

The remote session opens in a new browser tab. Close the tab to end the session.

Live shell

Click PowerShell, Bash, cmd, or zsh on the device detail page to open an interactive terminal.

  • Full PTY with ANSI colour support

  • Tab completion, command history, and terminal tools (vim, less) all work

  • Real-time keystroke delivery

  • Output captured and logged

The shell opens in a new browser tab with a full-screen terminal emulator.

Screenshot

Click Screenshot on any device to capture a single frame of the current screen without opening a remote session. Useful for quick checks. The image displays in a modal with the capture timestamp.

End-user chat

During remote sessions, operators can open a chat window on the end user's screen. The end user sees a small pop-up and can exchange messages in real time. Chat history is stored and visible in the device timeline.

Chat supports:

  • Direct mode: one operator and one end user

  • Team mode: multiple operators and one end user

Service and process control

From the device detail page on a paid plan:

  • Services tab: view Windows services with their status and start type. Start, stop, restart, enable, or disable services inline.

  • Processes tab: view running processes with PID, name, user, CPU usage, and memory. Sort by any column. Kill a process with confirmation.

Session security

  • All remote sessions require operator authentication

  • Sessions are logged in the audit trail with start time, end time, and operator identity

  • WebRTC traffic is encrypted end-to-end

  • Terminal sessions use WebSocket over TLS