Remote screen control
Server-side session recording for remote control — force recording, retention, auto-purge, the recorded-session browser — the streaming modes and clipboard an operator sets inside a session, the audio call to the signed-in user, what the web console, the Relay App and the NetLock app offer inside a session, pasting files into the session, touch input in the NetLock app, and viewing and controlling Android devices.
Remote screen control
The Remote Screen Control page at /settings/remote-screen is where a deployment operator decides whether remote control sessions are recorded, how long those recordings stay on disk, and where they are watched, downloaded, or deleted when something needs reviewing. It is an audit-and-compliance page, not a connection page. Several sections of this chapter describe the viewers instead of server settings:
- A.7.5 and A.7.6 cover the stream mode and the clipboard an operator sets inside a running session.
- A.7.8 to A.7.11 describe input, the three viewers (web console, Relay App, NetLock app), pasting files into a session and the touch input of the NetLock app.
- A.7.12 covers viewing and controlling Android devices.
How a session reaches the device (the agent streams JPEG frames through the NetLock server to the viewer) is outlined in Chapter 3.5. Nothing on this admin page changes how sessions connect; it only controls what the server does with a recording once a session has ended.

A.7.1 Recording behaviour
Two controls drive the recording behaviour for the whole deployment.
Force session recording: a single toggle at the top of the page. When on, the Remote Server records every remote control session that any operator starts against any device. Recording cannot be declined by the operator and is not surfaced as a per-session option; the policy is deployment-wide. When off, no server-side recording is performed. The field description on the page reads "When enabled, all remote screen control sessions will be recorded by the server."Save: the toolbar action that persists the toggle. Changes do not apply to sessions already in progress; a recording started under the old setting continues to behave as it did when it began.
Without the toggle, an operator can still record a single session from the viewer. Every viewer shows a running recording, a forced one included, for as long as it runs; see Recording in the viewers.
Note: The recording is produced by the Remote Server, not by the operator's browser. You do not need any client-side capture software, and the session being recorded does not reveal itself to the remote user any differently from an unrecorded session. Treat the toggle as a compliance decision: once it is on, every session is evidence, and every operator should be told so.
A.7.2 Retention and auto-purge
Compliance requirements rarely call for keeping recordings indefinitely. Two fields manage their lifetime:
Auto purge: a checkbox that enables automatic cleanup on a rolling window. When off, recordings are kept until an operator deletes them from the session browser.Older than X days: the retention window, in days. Recordings older than the chosen value are removed on the next purge cycle. Valid range on self-hosted deployments is1to9999days.
Cloud only: On cloud deployments, the retention window is fixed at seven days and the numeric field is hidden. The page shows the text "Your recordings will be kept for seven days." instead. To keep recordings longer on cloud, download the ZIP before the seven-day window elapses (see A.7.3).
Self-hosted operators can use the whole range. With Auto purge set to 1 day, recordings are kept just long enough to review them on the day they happen. A value of 9999 keeps them practically forever; plan disk space for that as for any long-lived evidence store, and review the capacity periodically. Auto purge deletes recordings older than the threshold and nothing else.
A.7.3 The recorded-session browser
The lower half of the page is a table of recorded sessions. The table fills when you click Load Sessions in the toolbar.
Each row represents one recorded session, with three row actions:
View: opens the Recording Session Viewer, an in-Console playback dialog. Use this for quick review without copying the recording off the server.Download ZIP: packages the session's files into a zip archive and triggers a browser download. Use this when evidence has to leave the server, for example for an external auditor, a ticket attachment, or a long-term archive outside the retention window.Delete: opens a confirmation dialog and, on confirm, deletes the session directory. Deletion is immediate and not undoable. The auto-purge setting does not replace the button; operators still need manual delete for sessions they want gone sooner than the window allows.

If a session row is missing from the table after Load Sessions, check whether the session actually fell into the current retention window. Auto-purge may already have removed it.
A.7.4 Interactions with other settings
- Viewers. The
Force session recordingtoggle applies to every session, whether it was opened from the web console, the Relay App or the NetLock app (A.7.9). - Maintenance mode. Maintenance mode suppresses notifications but does not suspend recording. A session started during maintenance is still recorded if the toggle is on. See A.2 for maintenance-mode semantics.
- Per-operator opt-out. Operators cannot opt out. Session recording is enforced at the server, not at the operator's workstation, so no client-side setting can bypass it.
A.7.5 Streaming modes
Every remote control session streams the device's screen as JPEG frames. The operator sets how sharp, how smooth and how large that stream is, per session, with the Stream mode selector in the viewer; no server-side setting is involved. This section lists the modes, where the selector sits, what the statistics overlay shows, what an older agent does, and how the screen is captured on the device.
The five modes
| Mode | Colour | JPEG quality | Frame rate | Resolution (longest edge) |
|---|---|---|---|---|
Quality | 4:4:4 | high, fixed | up to 20 fps | native |
Balanced (default) | 4:2:0 | adaptive | up to 30 fps | up to 2560 px |
Performance | 4:2:0 | adaptive, lower range | up to 60 fps | up to 1600 px |
Auto | 4:2:0 | adaptive, stepped down under congestion | 15 to 60 fps | 1280 to 2560 px |
Custom | as set in the advanced panel |
Qualitykeeps the full colour resolution (4:4:4), so small text and colour edges show no fringes, and streams the screen at its native size. Pick it for reading, detail work and screenshots; the frames are large.Balancedis the default of the web console and the Relay App; the NetLock app starts withAuto, which suits a mobile connection better. The device adjusts the JPEG quality within a middle range to the amount of change on the screen.Performancefavours motion: up to 60 frames per second, a lower quality range and a resolution ceiling of 1600 px. Pick it for video, animations and fast interaction.Autostarts with the Balanced settings and then steps the frame rate, the resolution ceiling and the quality up or down while the session runs. It reacts to four signals, measured once per second in the viewer: the frame rate actually received against the requested one, the round-trip time to the agent, the time the viewer needs to decode a frame, and frames that were superseded by a newer one before they could be shown. Under congestion it steps down at most once every two seconds; after several seconds of headroom it steps back up, one step at a time. Colour stays 4:2:0 inAuto; 4:4:4 is only available inQualityandCustom.Customuses exactly the values of the advanced panel: frame rate (5, 10, 15, 20, 30, 45 or 60 fps), quality (Autofor adaptive quality, or the fixed levelsHigh,MediumandLow), chroma (4:2:0or4:4:4) and resolution (Autofits the viewer window,Fullis the native size,Savercaps the longest edge at 1600 px). Touching any of these values while a preset is selected switches the mode toCustomautomatically.Customapplies no mode ceiling, soFullreaches the native resolution.
The resolution is a ceiling, not a target: a frame is never larger than the screen, and in Auto resolution never larger than what the viewer window can show. The mode is per session and stays selected across monitor switches.
Where the selector is
- Web Console. The
Stream modeselect sits in the viewer toolbar directly afterZoom. The advanced panel is theStreaming settingspopover (tune icon) further right in the same row; the statistics overlay is toggled with theStatisticsbutton next to it. - Relay App. The
Modepicker is in the second toolbar row of the viewer window, next to the resolution picker.Advancedreveals a third row withFPS,QualityandChroma; it opens on its own whenCustomis selected.Statstoggles the statistics panel. - NetLock app.
More→Streaming settingsopens a sheet with the five modes and their descriptions, and underAdvancedthe frame rate, quality, chroma and resolution. The statistics button in the viewer toolbar shows the statistics panel.
Changes apply to the running stream at once. Nothing reconnects, the session is not interrupted and a recording in progress continues. On a screen where nothing moves, the new settings show with the next periodic refresh, within four seconds.
The statistics overlay
The overlay is the place to judge a mode and to see what the connection is doing. Its values:
Mode: the selected mode.FPS: two numbers: frames shown in the viewer per second, and frames received from the agent per second (shown / receivedin the Web Console,shown / sentin the Relay App). A gap between the two means the viewer cannot keep up.Bandwidth: the received stream in kbit/s, smoothed over the last seconds. A static screen sits near zero.Frame size(Relay App:Avg Frame): the average size of a frame in KB.Decode: the time the viewer needs to decode one frame, in milliseconds.Encode: the time the device needs to compress one frame, in milliseconds, as reported by the agent.Round-trip time(Relay App:RTT): the round trip between the viewer and the agent, measured with a probe every two seconds.Resolution: the size of the streamed frame and, after the@, the frame rate the device actually achieves.Capture method(Relay App:Capture):dxgiwhen the screen is captured with the Desktop Duplication API,gdiwhen the classic capture is in use (see Capture on the device).QualityandChroma: the JPEG quality and colour subsampling of the last frames.Dropped frames(Relay App:Dropped): frames that arrived but were superseded by a newer one before they were shown. A steadily rising count means the connection or the viewer is behind;Autoreacts to it.Adaptive step(Relay App:Adaptive): inAuto, the current step of the adaptive controller: 0 is the Balanced baseline, positive steps reduce the load, negative steps raise the frame rate.
The Relay App and the NetLock app additionally list the codec, the total data received and the number of frames.
Where the choice is stored
- Web Console: in the browser's local storage (mode, chroma, frame rate, quality, resolution mode and whether the overlay is visible). The choice is per browser and per Console address; another browser or a private window starts with
Balancedagain. Nothing is stored on the server or per account. - Relay App: in the app's own settings store (
session_settings.datin its application data directory), so the choice applies to every session opened from that installation of the app. The resolution mode, the clipboard switch and whether the statistics panel is visible are kept there as well. - NetLock app: in the app's settings on the phone (mode, advanced values, statistics panel and the touch settings of A.7.11), for every device opened from that phone.
Agent requirement
Stream modes need an agent of version 3.3.0.1 or newer on the device. With an older agent the session still works: the stream runs with the settings that agent supports, the viewer shows a hint next to the mode selector, and a mode change is translated into the closest frame rate and quality the old agent understands (at most 30 fps and always 4:2:0). Update the agent to get 60 fps, 4:4:4 and the adaptive quality ranges.
A macOS device is offered for screen control and the end user chat only from agent 3.3.0.11 on: the device page, the tool window, the Relay App and the NetLock app leave the entries out for a Mac on an older agent instead of opening a session that cannot deliver a picture.
Capture on the device
On Windows the screen is captured with the Desktop Duplication API and falls back to the classic GDI capture automatically wherever duplication is not available: headless devices, RDP sessions, the lock screen and UAC prompts, devices running on the Microsoft Basic Display Adapter. The fallback is decided per screen and per frame; the device retries Desktop Duplication on its own, and the overlay's Capture method shows which one is active. Every mode works on both paths; only the CPU cost differs.
A screen where nothing changes costs almost nothing: the device sends a small "unchanged" reply instead of a frame, and re-sends the full picture every four seconds so that a viewer joining late, or a monitor switch, always gets an image.
Performance mode on a weak endpoint does not run the device dry: when capture and compression together take more than 80 % of the frame interval, the device halves the effective frame rate on its own and raises it again when there is headroom. The overlay's Resolution row shows the frame rate the device actually achieves.
Note: On Linux (Wayland, see X.8.5) the frame-rate cap and the resolution ceiling of a mode apply; quality and chroma are decided by the capture tools on the device and are not changed by the mode.
On macOS (agent 3.3.0.11 or later, see X.8.6) the screen is captured with ScreenCaptureKit, one stream per display. Every mode applies as on Windows: frame rate, resolution ceiling, quality range and chroma, the "unchanged" reply for a still screen with the full picture every four seconds, the frame-rate reduction on a busy device, and the statistics overlay, whose Capture method shows sck.
When a stream does not start or stops delivering, the device takes single pictures instead until a stream works again. The picture needs the screen recording permission on the Mac and the input the accessibility permission; the remote control window names the one that is missing. The pointer is not part of the picture; the viewer shows its own, as on Windows.
Recording
Recording works in every mode. The Remote Server samples the frames as they are streamed, so a recording carries the resolution and quality of the mode that was active; the Force session recording toggle in A.7.1 applies regardless of the mode.
A.7.6 Clipboard
Text travels in both directions of a remote control session. Which directions are active is decided in the viewer with the Clipboard switch, per operator and per session, like the stream mode in A.7.5. No policy or server setting controls it: a second operator in the same session has their own switch, and the device is told about it for as long as that viewer's session lasts.
Only text is transferred; see What is transferred.
Pasting into the session
Ctrl+V in the viewer reads the operator's own clipboard in the browser and sends the text with the keystroke, so the paste lands in the application that has the focus on the device.
In the NetLock app the same is done with More → Paste from phone, which sends the text of the phone's clipboard.
Files are handled separately. Files copied in the operator's file manager and pressed in with Ctrl+V, dropped onto the picture or chosen with Send files are sent to the device as files and pasted there; see A.7.10.
Taking the remote clipboard with Ctrl+C
Ctrl+C in the viewer is forwarded to the device, which injects the copy into the focused application and then waits for the clipboard to actually change before it answers. The device waits up to about half a second for the copy to land and then sends the text.
A clipboard that did not change within that budget is answered as empty. The operator's clipboard then keeps what it holds instead of receiving the value the copy was meant to replace, and the viewer says so.
Automatic sync of what the end user copies
While the switch is on, the device reports every change of its own clipboard, however the end user produced it, for example with the context menu's Copy, an application's own copy button, or a shortcut pressed at the device itself. Nothing has to be pressed in the viewer, and the text lands on the operator's clipboard as it arrives.
What the device applies before it reports a change:
- An empty clipboard is never reported; it would clear the operator's clipboard.
- Content that is not text is skipped.
- Text the operator has just pasted into the session is not handed straight back to them.
- Changes that fall close together are coalesced: at most one report every 250 ms, carrying the value the clipboard holds by then.
- The clipboard as it stands when the first viewer subscribes is a baseline, not a change. Reporting starts with the first copy after that.
Reporting runs only while at least one viewer of the session asked for it and stops with the last one. It is not session activity, so a session in which nothing else happens still reaches its inactivity timeout.
Looking at the remote clipboard without taking it
The View remote clipboard button next to the switch opens a dialog showing what the remote session's clipboard holds at that moment. It only reads the clipboard:
- No copy is injected on the device. The end user's selection and the end user's clipboard stay exactly as they were. That is what separates the dialog from
Ctrl+C, which necessarily copies whatever is selected in the focused application. - The operator's own clipboard is not touched either. The text reaches it only when the operator presses
Copy to my clipboardin the dialog.
Refresh asks again; the character count of the answer is shown below the text. Where there is nothing to show, the dialog says why, inline instead of as a toast: the clipboard is empty, it holds something that is not text, the content is too large, it could not be read, or the device did not answer within eight seconds. The last two offer a retry.
The dialog is useful alongside the automatic sync in three situations:
- with the switch off, when you want to see what the end user has without taking it;
- at the start of a session, because the automatic sync only reports changes from the moment it begins and does not see what was already on the clipboard;
- where the sync is not available on the device at all.
The clipboard switch
The switch governs both directions at once: a paste into the session, and the device reporting its own clipboard changes. It is on by default.
- Web Console.
Clipboardin the viewer toolbar. The choice is remembered per browser, next to the stream settings; another browser or a private window starts with it on again. Nothing is stored on the server or per account. - Relay App. The
Clipboardcheckbox of the viewer window, on by default. - NetLock app.
Clipboard syncin theMoremenu of the viewer.
In the web console and the Relay App the switch also decides whether Ctrl+V with copied files sends those files (A.7.10); dropping files and Send files work with the switch off.
The device is told the state of the switch once the session is streaming and again on every change. Turning it off stops the reporting at the device, not just in the viewer.
Reporting also follows the session's access state. While the session is not granted (the end user has not accepted, or the grant has lapsed), the device does not report clipboard changes and does not answer a request for its clipboard, even if the switch is on. That is re-evaluated for the running stream, not only when the switch is touched.
Platform coverage
Automatic sync works on Windows, macOS and Linux:
| Platform | Required tool |
|---|---|
| Windows | None. |
| macOS | None. On macOS 15.4 and later the content is read only while the clipboard access of NetLock RMM User Process is set to Always Allow on the Mac; otherwise automatic sync stays off and Ctrl+C and the view dialog read on request, which macOS may confirm with the user at the Mac (see X.8.6). |
| Linux — Wayland | wl-clipboard |
| Linux — X11 | xclip or xsel |
| Linux — none of these tools installed | No automatic sync, and no clipboard at all. |
A Linux session with none of wl-clipboard, xclip or xsel cannot reach its clipboard in either direction. Ctrl+C and the view dialog are answered with "The clipboard of the remote device cannot be accessed in this session", and no copy is injected for a request that cannot be answered. Install one of the tools (wl-clipboard on Wayland, xclip or xsel on X11) to enable it; see X.8.5.
What is transferred
Text only. Files, pictures and rich text are never transferred in either direction:
- On the automatic sync, a copied file or picture is skipped without a message. Copying a file is normal use, and the viewer would otherwise show a message every time the end user copies one.
- In the view dialog, where the operator asked for the result, the device distinguishes the two cases on Windows and reports "The clipboard of the remote device holds content that is not text" instead of claiming an empty clipboard. On macOS and Linux the clipboard is read through tools that hand out text only, so both cases arrive as an empty clipboard.
- To move files to the device, paste them into the session as described in A.7.10.
At most 1 MiB. Content larger than 1 MiB of UTF-8 text is not transferred, and it is not shortened either. The operator is told ("The clipboard content of the remote device is too large to transfer"), once per copy rather than on every poll.
Browser prerequisites (Web Console)
Writing to the operator's clipboard is done by the browser, under the browser's own rules.
- A secure context. Serve the Console over HTTPS (
localhostalso counts). Otherwise the browser can refuse clipboard writes. - A focused tab. Text arriving from the device is a server push, not a click, and that is the state in which browsers refuse a clipboard write. This shows most visibly when the viewer sits on a second monitor, the developer tools have the focus, or the tab is in the background. The Console therefore retries the write once on the operator's next click or keypress and says so meanwhile: "Clipboard received. Click into the session to apply it." Click into the session and the text is on the clipboard. Only the newest text is held, and the retry expires after 30 seconds.
The view dialog is not affected by this: its Copy to my clipboard happens inside the operator's own click.
Agent requirement
The automatic sync and the view dialog need an agent of version 3.3.0.1 or newer on the device; they are advertised separately, because reading the clipboard on request works wherever the clipboard can be read at all, while reporting changes depends on the platform. With an older agent the session still works and pasting into it is unaffected:
- The viewer shows a hint next to the
Clipboardswitch ("This agent version does not sync the clipboard automatically") andCtrl+Cin the viewer still works. - The
View remote clipboardbutton is present but disabled, with a tooltip that says why. A request the device cannot answer is never sent, and a request that does go unanswered leaves the dialog after eight seconds with a retry rather than spinning.
The Relay App and the NetLock app carry the switch, the device's messages and the view as well: View remote clipboard in the toolbar of the Relay App, More → View remote clipboard in the NetLock app while the picture runs. Both show the text read-only with its character count and Copy to my clipboard, wait eight seconds for the answer and name an empty clipboard or content that is not text. A text longer than 64 KB is shown cut off with a note; Copy to my clipboard still takes the whole text. With an older agent the Relay App disables the button with the reason as tooltip, and the NetLock app shows the reason instead of the text.
Audit
Clipboard transfers are not recorded in the audit trail. Neither direction is logged: a paste into the session, the answer to Ctrl+C, an automatic report and a look with the view dialog leave no audit entry. None of the transferred content is written to the audit trail, the server logs or the device's logs. The device's own log records the outcome and the length of a transfer, never the text.
The start and the end of the remote control session itself are recorded (see A.9 and, for sessions from the Relay App and the NetLock app, Audit of app sessions), and session recording under A.7.1 captures the screen, so a paste that becomes visible on the device appears in the recording like anything else on screen.
A.7.7 Audio call
The end user chat can be turned into a voice call. An operator calls the signed-in user of a Windows device from two places: the phone icon in the title row of the end user chat popup (which rings the session the chat talks to) and the phone icon in the title row of the remote screen control dialog, which opens the chat popup and places the call as soon as the session picker has settled. The audio travels as Opus packets through the NetLock server over the same hub that carries remote control sessions; no additional port and no direct connection between the browser and the device are needed.
What the user sees
The tray icon of the device shows an incoming call window with the operator's name and picture, plays a ring tone and waits 45 seconds for Accept or Decline; without an answer the call times out and the operator is told so.
After accepting, the user's default microphone and playback device are in use; the call window on the device lets the user change both devices, mute the microphone, switch echo suppression and hang up, and it shows the level of both sides and the duration.
The operator has the same controls in the console: a call bar under the title row of the chat popup with the state (calling, ringing, connected with the user's name), the duration, mute, the microphone and playback device pickers, level meters and Hang up. Either side can end the call; closing the chat popup or switching the user during a call asks the operator for confirmation first.
Requirements
- Permission. The account needs
devices_remote_audio_call("Audio call" in the permission editor, directly under Remote Control). Members of the built-in Administrator role hold it automatically; every other account or role has to be granted it. Without the permission the phone icons are not rendered and the server refuses the call. - Policy. On the Agent tab of the policy,
Allow audio callssits in the Remote Control block belowRemote Screen Control(see §6.4). It is on by default and only takes effect while remote screen control is enabled in the same policy; a policy with remote screen control off cannot carry calls. The texts of the incoming call window (title, message with{operator}replaced by the operator's name, and the Accept, Decline and Hang up buttons) are edited in theAudio Callblock of the Tray Icon tab (§6.5); empty fields use the English defaults. A change of the policy reaches the server's check within about 30 seconds. - Device. Windows only. Requires agent 3.3.0.5 or later with the tray icon running in the user's session. A device with an older agent answers "agent update required"; a device without a signed-in user, without a running tray icon, or a Linux or macOS device shows no phone icon or reports the call as not supported. Mobile devices cannot be called.
- Browser. The operator's browser needs WebCodecs with the Opus codec, an AudioWorklet and microphone access: Chrome and Edge, Firefox 130 or later, Safari 26 or later. A browser without this support shows a toast and nothing else. The console asks for the microphone permission of the site on the first call; a refused permission is reported as a toast, and the call is not placed. The playback device picker is hidden in browsers that cannot route audio to a chosen output (no
setSinkId).
Headset and echo
The operator's browser applies its own echo cancellation, noise suppression and automatic gain control to the microphone. On the user's side there is no acoustic echo canceller: a user on speakers is heard back by the operator with a delay unless echo suppression is on, which lowers the playback while the user speaks. A headset on the user's side avoids the effect altogether, and the call bar in the console says so.
What is recorded
Calls are not recorded. Session recording (A.7.1), including forced recording, applies to screen sessions only; an audio call never produces a recording. Each call is kept as an entry of the remote control session history with the time of the call, the accepted time as its start, the duration and how it ended (declined, not answered, hung up by the operator or the user, connection lost, or not supported with the reason). The console audit log records "Audio call started" and "Audio call ended" with the reason for the operator's account. The audio itself is never stored.
One call per device session at a time: a second operator who calls the same user while a call is on is told that the user is already in a call, and a repeated call to the same device within a few seconds is asked to wait.
A.7.8 Keyboard and mouse
Keyboard input goes to the device once the remote screen has been clicked; it keeps going there in fullscreen and after leaving fullscreen. In fullscreen in Firefox and Safari, Esc ends the fullscreen view (a browser rule) and does not reach the device; for Chrome and Edge see Full screen in Chrome and Edge. With agent 3.3.0.11 or later, Ctrl and Shift held during a mouse click or a wheel turn reach the device as well, so Shift+right-click (for example Run as different user on Windows), Ctrl+click and Shift+click selections work. Firefox always shows its own context menu on Shift+right-click in addition to the device's menu; this is browser behaviour that a web page cannot switch off, so close the browser menu with Esc or use Chrome or Edge for this shortcut.
On a macOS device the modifiers of a Windows or Linux keyboard are translated: Ctrl is applied as Command, the Windows or Meta key as Control and Alt as Option, for keyboard shortcuts as well as for clicks and the wheel. When the viewer runs on a Mac too, the keys are sent as they were pressed, so Command stays Command and Control stays Control; this applies to the Web Console and the Relay App. The Ctrl+Alt+Del button sends Command+Option+Esc to a Mac. See X.8.6 for the permissions the input needs there.
In the Relay App the pointer reaches the device while it moves over the picture, also without a pressed button, so hover effects and tooltips on the device appear. Ctrl and Shift go with clicks and the wheel, as in the web console. A horizontal wheel or a sideways swipe on a touchpad is sent as Shift+wheel, which applications on the device read as horizontal scrolling. Two keys stay with the Relay App:
Ctrl+wheel (Command+wheel when the Relay App runs on a Mac) zooms the picture and never reaches the device. On a Mac,Control+wheel is sent to the device as a wheel turn withCtrl.F11switches full screen on and off and is not sent. Unlike in the browser,Escin full screen goes to the device; leave full screen withF11or theExit full screenbutton.
In the NetLock app input works by touch, in one of two modes; see A.7.11.
Keyboard shortcuts
Some shortcuts never reach the browser, because the operator's own computer keeps them: the Windows or Super key on its own and its combinations (Win+D, Win+R, Super+D), Alt+Tab, Ctrl+Shift+Esc and, depending on the system, Alt+F4, F11 and Print. The shortcut button (⌘ icon) next to Ctrl+Alt+Del in the toolbar opens a menu that sends them to the device. It lists the shortcuts of the device's operating system:
| Device | Shortcuts in the menu |
|---|---|
| Windows | Start menu (Win), Show desktop (Win+D), File Explorer (Win+E), Run dialog (Win+R), Quick link menu (Win+X), Task view (Win+Tab), Lock screen (Win+L), Switch window (Alt+Tab), Close window (Alt+F4), Task Manager (Ctrl+Shift+Esc), Escape (Esc), Toggle full screen (F11), Screenshot (Print) |
| macOS | Switch app (Command+Tab), Spotlight search (Command+Space), Quit app (Command+Q), Close window (Command+W), Hide app (Command+H), Mission Control (Control+↑), Toggle full screen (Control+Command+F), Lock screen (Control+Command+Q), Escape (Esc) |
| Linux (GNOME, KDE Plasma) | Activities overview (Super), Show desktop (Super+D), Show applications (Super+A), Switch window (Alt+Tab), Close window (Alt+F4), Run a command (Alt+F2), Open terminal (Ctrl+Alt+T), Toggle full screen (F11), Escape (Esc), Screenshot (Print) |
The macOS shortcuts are sent as listed, with Command, Control and Option of the Mac; the modifier translation described above does not apply to them.
The last entry, Win + next key (Super + next key on Linux, Cmd + next key on macOS), covers combinations that are not in the list, such as Win+Shift+S or Win+V: the next key you press goes to the device together with that key, then the menu returns to normal. While it waits, the shortcut button is highlighted and a note is shown on the remote screen; Esc or choosing the entry again cancels it. On a phone or tablet the next character typed on the soft keyboard is used.
- Each shortcut is pressed and released at once.
Alt+TabandCommand+Tabtherefore switch to the previous window only; to choose any open window, use Task view (Win+Tab) or Mission Control. - What a shortcut does depends on the settings of the device.
Super+Dshows the desktop on Ubuntu and KDE Plasma but is not assigned on a standard GNOME desktop (Fedora, for example); useSuperorAlt+Tabthere.Alt+F2andCtrl+Alt+Tare GNOME and Ubuntu shortcuts. Ctrl+Alt+Delstays a button of its own. Its tooltip names what the device does with it: Windows shows its security screen, a Mac opens Force Quit Applications (Command+Option+Esc), Linux opens the log out dialog of the desktop.- On a phone or tablet the menu is also the way to send
Esc, which the soft keyboard does not have.
The Relay App offers the same menu, including the + next key entry, under the Shortcuts button next to Ctrl+Alt+Del. In the NetLock app, More → Keyboard shortcuts lists the same shortcuts; for other combinations use the latched Win key of the key bar (A.7.11).
Full screen in Chrome and Edge
In full screen, Chrome and Edge hand the keyboard to the remote screen. Esc, the Windows key on its own and combinations such as Win+D or Alt+Tab then go to the device, as far as the operator's operating system releases them to the browser; Ctrl+Alt+Del and Win+L always stay with the operator's computer (use the button and the menu for them). To leave full screen, hold Esc for two seconds; the browser shows a note about it when full screen starts. The browser may ask once whether the console may use the keyboard; if this is refused, full screen works as in Firefox.
Firefox and Safari do not offer this: there Esc leaves full screen, and the keyboard shortcut menu in the toolbar is the way to send these keys.
A.7.9 The viewers
A remote screen session is opened from one of three viewers. All three talk to the same screen hub of the server and to the same agent, so what the device does is the same; they differ in how they are operated and how they sign in.
| Web console | Relay App | NetLock app | |
|---|---|---|---|
| Opened from | Remote Control on the device | Tab Screen Control of the sessions window, Connect on a device | Relay profile → Screen control |
| Signs in with | the console account | a relay API key | a relay API key (relay profile) |
| Windows, Linux and macOS devices | Yes | Yes | Yes |
| Stream modes, advanced settings, statistics (A.7.5) | Yes | Yes | Yes |
| Zoom | Zoom in the toolbar | Fit or 25 % to 300 %, buttons or Ctrl+wheel | Pinch |
| Full screen | Yes; Esc leaves it (Chrome and Edge: hold Esc, A.7.8) | F11 or button; Esc goes to the device | The toolbar hides itself; the handle at the top edge brings it back |
| Keyboard shortcuts (A.7.8) | Shortcut button (⌘) in the toolbar | Shortcuts button | More → Keyboard shortcuts |
| Recording indicator, start and stop | Yes | Yes | Yes |
| View of the remote clipboard (A.7.6) | Yes | Yes | Yes |
| Paste files (A.7.10) | Yes | Yes | No |
| Touchpad mode (A.7.11) | — | — | Yes |
| Screenshot | — | Copy to clipboard, Save as… (PNG) | More → Screenshot |
| Anchored devices (A.13.9, A.13.10) | The console asks a registered phone for the grant | Waits for the approval in the NetLock app | Signs on this phone or waits for another phone |
For the Relay App and the NetLock app, the server lets a relay API key open a screen session only when the key's Screen control switch is on (Relay Server → Manage API Keys) and the account that owns the key holds devices_remote_control and the device's tenant. The account that owns the key is the account the session runs under: it is shown on the device, it is written to the audit log, and its permissions decide what the session may do.
Recording in the viewers
While the server records a session, every viewer shows a red REC chip, from the first picture to the end of the recording. The chip follows the recording state the server reports, not a local setting, so a recording started by another viewer of the same session, or forced by Force session recording, is shown as well. The Relay App and the NetLock app write REC (forced) for a forced recording; the web console shows REC with the tooltip "This session is recorded by policy and cannot be stopped." In the NetLock app the chip stays visible while the toolbar is hidden.
| Start and stop | |
|---|---|
| Web console | Start recording and Stop recording in the toolbar; a click on the chip stops as well. |
| Relay App | The recording button in the toolbar, enabled while the picture runs. |
| NetLock app | More → Start recording or Stop recording while the picture runs. |
A forced recording cannot be stopped: the web console offers neither button, the Relay App disables its button, and the NetLock app answers with the policy hint. A stopped recording is reported as "Recording saved (n frames)." or, without any frame, "Recording stopped, no frames were captured."; a start is refused with a message when the storage limit of the instance is reached. When the server ends a recording on its own (storage limit reached, the frame limit of a session reached, a write error), the viewer says so.
When the Relay App or the NetLock app opens a new hub session for the same window (after a connection loss, after switching the session, and in the NetLock app after returning from the background), a recording the operator started is started again. A recording that the server ended does not start again.
Another technician on the device
Before a session starts, the viewer asks the server how many screen sessions other viewers hold on the device. Web console, Relay App and NetLock app sessions are all counted; backstage sessions are not. When there is at least one, the viewer shows "Another technician is already connected to this device. Proceed with caution to avoid conflicts." for ten seconds. It is a hint, not a block: the session starts as usual. The web console shows it once per remote control dialog, the apps once per window when the session first starts, not again after a reconnect.
Waiting for the first picture, black picture, lost signal
The viewers name the states in which no usable picture arrives, as non-blocking notices at the upper edge of the picture; input keeps working while they show.
- "Waiting for the first picture from the session." means that the device answers, but no picture arrived since the stream started. When the state lasts, the line "The agent on the device may need an update." is added.
- "The remote screen is showing a black picture." means that the viewer samples the shown picture at regular intervals and found it black several times in a row, for example a switched-off display or a session that draws nothing. A pointer, a line of text or a spinner on a black background does not count as black.
- No signal: when the picture stops, the last picture stays visible, dimmed, with the reason above it.
Retryasks again;Switch sessionmoves to another user session of the device, orConnect anywayconnects to the selected session regardless.
Linux devices: consent and capture start
Linux devices can be controlled from all three viewers. On a Wayland device the desktop asks the user for the screen-sharing permission on the first connection. Instead of No signal, the viewers show what the device is doing:
| Message | Meaning |
|---|---|
| Waiting for the user to accept screen sharing on the device. | The screen-sharing dialog is open on the device. |
| Starting the screen capture on the device. | The capture is starting and the first picture is not there yet. |
| Screen sharing was not accepted on the device. | The dialog was declined or not answered. |
| Screen capture components are missing on the device. See the Linux prerequisites in the documentation. | A package of the capture path is missing on the device. |
The prerequisites and the troubleshooting are in X.8.5.
When a session does not start
The server answers a refused session start with a reason, and every viewer shows it as a sentence in the operator's language:
| Reason | Text in the viewer |
|---|---|
| Device offline | The device is offline. It is not connected to the NetLock RMM server. |
| Device not found | The device was not found. |
| Other tenant | Access denied for this device's tenant. |
No permission, or the relay key's Screen control switch is off | The web console shows its permission message; the apps show Remote control is not allowed for this relay key or account. |
| Request not queued | The request could not be queued for this device. Please try again. |
| Approval required (anchored device) | The apps show This device needs an approval in the NetLock app before screen control can start., see A.13.10. |
| Server could not check the device | The web console shows The server could not check the device right now. Please try again in a moment., the apps The server cannot process the request right now. Please try again in a moment. |
| Anything else | The screen control session could not be started. |
Relay App and NetLock app versions before 3.3.0.11 show a short code such as device_offline instead; update the app.
Who the device is told is connecting
The consent prompt and the support badge on the device show the name of the technician and, if the account has released its profile picture for end users, the picture. The server sets both from the account the viewer signed in with: the console account for the web console, the account that owns the relay key for the Relay App and the NetLock app. When the account cannot be read, the prompt shows the name of the relay key.
Audit of app sessions
The web console writes the start of a session into the audit log. For a session from the Relay App or the NetLock app the server writes the line Remote control session started (Relay key: <key name>) under the login of the account that owns the key. Recordings started or stopped from the apps, and forced recordings of app sessions, are written in the same way, with the key name.
Connection loss
After a short connection loss the Relay App and the NetLock app reconnect on their own, start the session again on the new connection and return to the same user session and screen. They retry for about two and a half minutes before they show Connection lost. The web console retries its connection to the server on the same schedule. The NetLock app ends the stream when it goes to the background or the phone is locked, and resumes it with the same user session and screen when it comes back.
A.7.10 Pasting files into the session
Files from the operator's computer can be sent into a running session and pasted on the device where the user is working, for example into the open Explorer or Finder folder, onto the desktop, or as a mail attachment. Several files go in one transfer.
How to send files
| Viewer | Ways |
|---|---|
| Web console | Drop the files onto the picture (every browser); the Send files button next to the file browser button (multiple selection); Ctrl+V with files copied in the file manager, in Chromium-based browsers such as Chrome and Edge. |
| Relay App | Drop the files onto the picture; the Send files button (multiple selection); Ctrl+V with files copied in the file manager. |
| NetLock app | Not available. |
Ctrl+V sends files only while the Clipboard switch of the viewer is on (A.7.6); with text on the clipboard it pastes the text. In the web console:
- Firefox does not hand copied files to a web page, so
Ctrl+Vthere always pastes text. Drop the files or useSend filesinstead. - A picture alone on the clipboard, for example a screenshot, is sent as a file
image.png, after the confirmation. - A copy from Office that carries text and formatting next to a picture, for example Excel cells, stays text.
While files are dragged over the picture, a frame with "Drop to send to the device" appears. A drop onto the picture never navigates the browser away from the console, even while no file can be sent; the frame then names the reason.
What happens
- The viewer asks once for confirmation, with the number of files, their total size and their names.
- It uploads the files to the server one after another. A list shows the state of each file (waiting, uploading with percent, uploaded, failed) and offers
Cancel; afterCancelnothing is pasted. - It sends the files that arrived to the device as one transfer. A file that failed to upload is left out.
- The device downloads the files, puts them on its clipboard as files and pastes them into the application in front. The list shows On the device for each file, and the viewer reports the result, for example "3 files pasted on the device." or "2 of 3 files were pasted."
Only one transfer runs per session at a time; a second one is refused with a message until the first has finished.
Limits
- Up to 100 files and 10 GB together per transfer; a single file can be up to 10 GB.
- Folders are skipped, with a notice; only files are sent.
- Names are cleaned the same way in the viewer and on the device: characters that Windows does not allow in file names (
< > : " | ? *) become_, reserved Windows names such asCONorNULget a leading_, and very long names are shortened with the extension kept. Two files with the same name in one transfer becomename.extandname (2).ext.
What the device does
| Device | Behaviour |
|---|---|
| Windows | The files are put on the clipboard as a file list to be copied, then Ctrl+V is pressed in the user's session. Where they land is decided by the application in front: the open Explorer folder, the desktop, an attachment in Outlook. |
| macOS | The files are put on the general pasteboard as file URLs, then Command+V is pressed. It goes to the application in front: a Finder window pastes into its folder, the Finder without a window pastes onto the desktop, Mail adds an attachment. The Finder is not brought to the front. Command+V needs the Accessibility permission of NetLock RMM User Process (X.8.6); without it the files stay on the clipboard and the viewer says that the user can paste them. |
| Linux (GNOME and KDE on Wayland) | The files are put on the clipboard with wl-copy from the package wl-clipboard, in the format the desktop's file manager reads, then Ctrl+V is pressed. The open file manager window pastes them. Without wl-clipboard, outside a Wayland session, or when the clipboard cannot be set within five seconds, the files are copied into the user's Downloads folder instead and the viewer shows the path. |
When the paste keystroke cannot be sent, the files are on the device's clipboard and the viewer says "The files are on the clipboard of the device, but the paste could not be triggered. The user can paste them there." (web console). When a step fails on the device, the viewer names it (not enough free space, no user session, download failed, the user session did not answer), together with the folder the files were stored in on the device, where one is known.
Where the files are kept
-
On the server the files are stored in the File Server folder
uploadedof the device, the same folder the file browser shows. They stay there until someone deletes them; a file with the same name is replaced. -
On the device the agent downloads them into a folder of its own per transfer, below
Clipboard Filesin the Remote agent's data directory, from which they are pasted. The folder belongs to the user the files are pasted for: only that account, the system account and administrators (root on Linux and macOS) can read it, and the user cannot place anything in it. In the device session of a Windows device that is the user signed in at the console.The clipboard of the device points to these copies, so the user can paste them again later; the agent removes them one day after the transfer. A transfer that was saved to the Downloads folder, in which no file arrived, or whose session ended during the download is removed right away.
Requirements
- Permission. Pasting files requires
devices_remote_file_browserin every viewer, checked by the server, next todevices_remote_control. For the Relay App it is the account that owns the relay key. Without it the web console shows noSend filesbutton and answers a drop with a message, and the Relay App reports "You are not permitted to send files to this device." - Agent. The device needs an agent that reports file paste, 3.3.0.11 or later. With an older agent
Send filesis disabled with the tooltip "The agent on this device cannot receive files this way. Update the agent to use it."; a drop is answered with the same notice, and nothing is uploaded. - Server. The Relay App sends files through the server; an older server is reported as "The server does not accept files from the Relay App. Update the server to use it."
- Anchored devices. On a device with endpoint protection, the grant of the running screen session (A.13.9) covers the paste; no separate approval is needed.
Audit
The web console writes one line per transfer it sent, for example Remote control: 3 file(s) sent to paste into the session ('a.pdf', 'b.pdf', 'c.pdf'), 1048576 bytes. The Relay App's uploads are written by the server, one line per file under the account that owns the relay key, with the key name. A transfer that was cancelled before anything was sent writes no line.
A.7.11 Touch input in the NetLock app
The NetLock app offers two ways to operate the remote screen with the fingers. The Touchpad button in the viewer toolbar switches between them, with a short notice. The choice is kept on the phone and applies to every device. Direct touch is the default; the first time a device with input opens, the app points once to the touchpad mode.
The touch modes need mouse and keyboard input on the device. On a macOS device without the Accessibility permission the button is greyed out; a tap on it explains why.
Direct touch
The finger acts as the mouse: a tap clicks where the finger touches the picture.
| Gesture | Effect |
|---|---|
| Tap | Left click where the finger is |
| Long press | Right click |
| Long press, then move | Drag |
Touch and move with Drag mode on (toolbar) | Drag |
| One finger, zoomed in | Moves the visible part of the picture |
| Two-finger tap | Right click |
| Two fingers moving | Scroll; the direction (vertical or horizontal) is fixed when the movement starts |
| Pinch | Zoom; two fingers move the zoomed picture |
| Two-finger double tap | Back to the whole screen |
Touchpad mode
The app draws a pointer over the picture and the fingers move it like on a laptop touchpad. Clicks always land at the pointer, not under the finger, which makes small targets reachable on a phone screen. The pointer is a white arrow with a black outline whose tip is the click point; it turns cyan while the left button is held. The device's own pointer follows with the delay of the connection. The pointer starts in the middle of the screen, and again after switching the screen or the user session.
| Gesture | Effect |
|---|---|
| One finger moving | Moves the pointer; slow movement is precise, fast movement covers distance |
| Tap | Left click at the pointer |
| Tap twice | Double click |
| Double tap and hold, then move | Drag: the button stays down until the finger lifts |
| Two-finger tap | Right click |
| Two fingers moving | Scroll at the pointer, up, down, left and right; the direction is fixed when the movement starts |
| Pinch | Zoom; while zoomed in, the picture follows the pointer when it reaches the edge |
| Two-finger double tap | Back to the whole screen |
A long press does nothing in this mode, so a resting finger does not right-click, and three or more fingers are ignored. In touchpad mode the Drag mode button is hidden; double tap and hold drags instead.
Touchpad settings (More → Touchpad settings):
Pointer speed: five steps fromSlowtoFast.Mouse button bar: shows a bar withLeftandRightabove the key bar, in touchpad mode only. A tap onLeftclicks; holdingLeftkeeps the button down, so a second finger on the picture moves the pointer and drags.Rightright-clicks. There is no middle button.Show gestures: opens the gesture card, which also appears once the first time the touchpad mode is switched on.
Key bar and modifiers
The key bar below the picture holds Esc, Tab, Ctrl, Alt, Win, Shift, the arrow keys, Del, Home, End, PgUp, PgDn, Ins and F1 to F12; the keyboard button opens the phone's keyboard for typing. A modifier is latched:
- A tap latches it for one use: it applies to the next key, click, drag or scroll and is released afterwards.
- A long press locks it until it is tapped again.
Ctrl and Shift apply to taps, clicks, drags and every scroll step in both touch modes, for example Ctrl+click to select several files or Shift+click to select a range. Alt and Win apply to keys only. On a macOS device the modifiers are translated as described in A.7.8.
When the app goes to the background, the phone is locked, a call comes in or the mode is switched while a button is held down (dragging, or holding Left of the mouse button bar), the app releases the button on the device first, so no button stays pressed.
A.7.12 Android devices
An Android phone or tablet enrolled with the NetLock RMM app can be viewed and, when its policy allows it, controlled from the web console. Open the device on Devices and choose View screen in the action bar; the button reads Control screen when the device's policy allows control. The Relay App and the NetLock app do not offer screen sessions to Android devices.
A person at the phone is always involved: Android asks its user for permission at the start of every session, and nothing can be shown or operated while nobody is at the device.
Requirements
- The account holds
devices_remote_control. The same permission covers viewing and controlling; Android needs no separate permission. - Opening a session passes the step-up authentication of the remote actions, as for every remote action on a desktop device, viewing included.
- For control, the device's policy has
Remote Screen Controlswitched on (Enableon theRemote Controlsub-tab of theAgenttab, see Chapter 6.4), the same setting as for desktop devices. ItsAccess modedoes not apply to Android: the phone always asks. Viewing does not depend on this setting. - The phone runs an app version with remote control, and its remote control service is switched on (see below). Typing text needs Android 13 or later; taps, swipes, scrolling and the system buttons work on every Android version the app supports.
- On a phone protected by endpoint protection, every screen session, viewing included, needs an approval on a registered phone (A.13.11).
Setting up the phone once
Control works through an Android accessibility service of the app, NetLock remote control. It does not read what is on the screen and collects no data; it only carries out what the technician does in the viewer, and only during a session the user allowed.
- While the device's policy allows control and the device is approved, the app shows the card
Remote controlwith the state of the service (Not set up yet. Until then, technicians can only see the screen.orReady.).Set up remote controlfirst showsAllow remote control?, which explains what the service does and does not do; afterAgree, Android's accessibility settings open. - Android opens the list of accessibility services, not the page of this one. The service appears in that list only after
Agree: the app ships it switched off and makes it available only while the policy allows control, and removes it again when the policy stops allowing it or the enrollment is removed. FindNetLock remote controlin the list (depending on the manufacturer under Installed apps or Downloaded apps) and switch it on. - If the app was installed from an APK file rather than from Google Play, Android shows the switch as Controlled by Restricted Setting at first. Open
Settings→Apps→NetLock RMM Agent App, tap⋮, chooseAllow restricted settings, confirm, and switch the service on again. The card shows this step on such installations. - On newer Android versions accessibility services cannot be switched on during a phone call. Set the service up before or after the call; the card says so as well.
Android may remind the user after some time that the service has access to the device. That is Android's own notice for services of this kind and can be confirmed.
Every session
- The technician opens the viewer. The request reaches the phone as a notification, A technician wants to see and control this screen (or An operator wants to view this screen for a view session); the user taps it.
- When the session may take input, the app asks first:
Allow remote control?with the text "{name} wants to see your screen and operate this phone: tap, swipe and type." and the buttonsAllow control,View onlyandDecline. The name is the technician's account name, set by the server. When the remote control service is not switched on yet, the question says that the technician will only see the screen. Without control the app asks only whether the screen may be shared. - Android then asks to start screen sharing. A control session always shares the entire screen. For a view session (also when the user chose
View only), the user chooses what to share, and from Android 15 the prompt preselects A single app: the viewer then shows only that app, and the rest of the phone stays hidden.
If the user declines, nobody answers in time or the phone cannot ask its user, the viewer says so at once.
In the viewer
While the picture is shown, the toolbar above it offers:
View/Control: the switch turns on by itself once control is available and can be turned off for viewing only. When control is not available it is greyed out and its tooltip names the reason: the policy, the account, the user chose view only, the service is not enabled on the phone, or the app is out of date.Back,Home,Recent apps,Notifications,Quick settingsandPower menu(with a confirmation; choosing an entry there can end the session).Long press: the next tap on the picture is held.KeyboardandPaste clipboard: on Android 13 and later.- A chip with the input state, and the recording chip when the session is recorded.
With control on, the picture works like a finger: click or tap to tap, hold to long-press, drag to swipe or move, the mouse wheel scrolls, a right click is a long press. Typed text goes into the field that is selected on the phone; Enter, Backspace, Delete, Tab, the arrow keys, Home and End work as editing keys, and Ctrl+V pastes the operator's clipboard as text. When the phone is rotated, the next picture arrives in the new orientation; an input made on the old picture is dropped with a notice.
On the phone during control
While control is active, the phone shows a red frame around the screen with the pill Remote control active and Stop, and the screen stays on. The notification of the session reads {name} can see and control this screen and has Stop sharing. Both Stop buttons end the whole session, the picture as well as the control; control cannot be stopped on its own. A finger on the screen interrupts what the technician is doing at that moment. Every end of the session (Stop on the phone, the viewer closing, the connection ending, the phone locking) ends the input at once.
Limits
- Somebody has to be at the device for every session; Android allows no unattended start and cannot be unlocked remotely.
- On recent Android versions locking the screen ends the session. The
Power menuis offered, but no lock button. - Apps that protect their content (banking apps, password fields) appear black in the picture but still receive taps. The viewer shows a hint when the picture is black during control.
- Some system dialogs (permission prompts, the package installer, parts of the settings) accept no input from accessibility services and cannot be operated remotely.
- When Android reports during a control session that the phone no longer shares its entire screen (Android 14 and later), control pauses and the viewer says so until the whole screen is shared again.
- One finger only: no pinch or multi-finger gestures. Nothing is copied from the phone to the operator.
- An app version without remote control shows the screen for viewing only; the viewer says so.
Recording and audit
A forced recording (A.7.1) covers Android sessions like any other; the viewer shows the recording chip. The audit log records Mobile screen view started or Mobile screen control started and each time the operator switches input on or off in the viewer. Single taps and typed text are not recorded in the audit log, and neither the server nor the app logs typed text or positions.
Permissions
settings_enabled: access to theSettingsgroup at all.settings_remote_screen_enabled: access to this page's toggles and session browser.devices_remote_audio_call: starting an audio call with the signed-in user of a Windows device (A.7.7); granted to the built-in Administrator role automatically.devices_remote_control: opening a remote screen session in any viewer, starting and stopping a recording and viewing the remote clipboard. For the Relay App and the NetLock app it is checked on the account that owns the relay key, together with the key'sScreen controlswitch. It also covers viewing and controlling Android devices from the web console (A.7.12); the server checks it again at least every minute while input flows.devices_remote_file_browser: pasting files into a session (A.7.10), in every viewer, checked by the server.
Related chapters
- Chapter 3.5 — Remote control — how remote control sessions are established and what transports are available.
- A.2 — Updates & maintenance — maintenance windows and notification suppression.
- A.9 — Logging & protocols — for server-side logs that record the start and stop of each remote control session.
- A.12 — Content defaults — related Settings sub-pages in Part IV.
- A.13 — Endpoint protection — screen control on anchored devices, from the console and from the apps.
- Remote-control a device with the Relay App — installing the Relay App and opening a session from it.
Whitelabeling & themes
Deployment-wide brand assets, a 40-field light-and-dark colour palette, theme import and export, and the Community Themes browser.
Notifications deep dive
Full reference for the five notification channels on the Notifications page: Email (SMTP), Microsoft Teams, Telegram, ntfy.sh, and Webhook.