Feature Matrix
A scannable overview of every NetLock RMM feature area and its platform support, with links to the chapter that documents each in full.
Feature Matrix
This appendix is a single-page index of what NetLock RMM does. It groups every feature into Console, server, and agent areas, records platform support where it varies, and links to the chapter that documents the feature in full. Use it to answer "does the product do X, and where do I read about it?", not as a configuration reference. For mechanics, follow the cross-links.
Three conventions apply throughout:
- Yes / No in a platform column means the feature is or is not available on that operating system.
- A dash (
—) means the feature does not apply to that platform. - Where a column names a tool or shell instead of Yes (for example
PowerShell), that is the platform-specific implementation.
Note: This matrix summarises shipped behaviour. When a feature area carries deployment-specific or licensing-specific limits, the linked chapter is authoritative.
X.7.1 Console features
The web Console is the interface operators work in. The features below are available regardless of agent platform; they are properties of the Console itself.
| Feature | Summary | Documented in |
|---|---|---|
| Multi-tenancy | Tenant, location, and group hierarchy for organising devices. | Chapter 4 |
| Users and roles | Per-user, permission-gated access; tenant-scoped visibility. | Chapter 14 |
| Two-factor authentication | Time-based one-time password (TOTP) on operator accounts. | Chapter 14 |
| Single sign-on | OpenID Connect with Azure AD, Google, Keycloak, Okta, or Auth0; one provider active at a time. | A.4 |
| IP whitelist and country restriction | Restricts Console access to named addresses, and Console and server access to selected countries. | A.4 |
| Rate limiting | Per-device request limits on the server with temporary blocks for devices and addresses that keep exceeding them; observe mode by default. | A.4.1b |
| Dashboard and Panel Builder | Per-user dashboards with chart and table panels from catalog widgets or custom SQL (visual query builder or direct SQL; custom SQL needs SQL access, self-hosted only). | Chapter 2 |
| Setup Wizard | First-run guided setup shown on the Dashboard. | Chapter 2 |
| Events browser | Operational event stream, filterable by severity, type, scope, device, and time. | Chapter 12 |
| Audit log | Record of administrative actions in the Console. | Chapter 12 |
| Notifications | Email, Microsoft Teams (Workflows webhook, Adaptive Card or plain text), Telegram, ntfy.sh, and webhook channels. | A.8 |
| Reports | Pre-built and custom reports, brand templates, and scheduled delivery. | Chapter 11 |
| Custom fields | Operator-defined device-detail tabs, sections, and fields; values per device or inherited from group, location, tenant and global level; secret fields with an audited reveal. | Chapter 8.4 |
| Script variables and write-back | Scripts read device data and custom field values through {{namespace.key}} tokens and can write values back into custom fields. | Script variables, Write-back |
| Public API | REST API under /v1 with Bearer tokens, scopes, tenant scoping and a Swagger reference served by the server. | X.9 |
| File Server | Stores files for distribution; files can be referenced from scripts. | Chapter 9.1 |
| AI Chat and assistants | Optional LLM features for chat and per-feature assistance. | Chapter 13, A.11 |
| Customer AI (end-user chat) | Optional AI assistant for end users in the agent tray, with an encrypted conversation history and per-user and per-tenant token limits. | Chapter 13.6 |
| Ticket System | Optional helpdesk: departments, SLAs, time tracking, templates. | Chapter 10 |
| Device World Map | Plots managed devices by IP geolocation. | Chapter 3 |
| Device Topology | Draws tenants, locations, subnets and devices as a network map inferred from the adapters the agents report; nodes can be dragged and the arrangement is kept per user. | Chapter 3 |
| Maintenance mode | Manual and scheduled windows that suppress outbound notifications. | A.2 |
| Database management | Per-table retention, cleanup, and an optional SQL console. | A.3 |
| Localization | Language, timezone, and date-format settings. | A.5 |
| Agent installers | Generates command-line configs and one-click installers for Windows, Linux, and macOS. | Chapter 3 |
| Whitelabeling | Branding of logos, colours, login page, and Console chrome. | A.6 |
| Community catalogues | Shared Scripts, Reports, and Themes through the Members Portal. | Chapter 15 |
Optional module: The Ticket System applies only when it is enabled in
Settings → Ticket System. See Chapter 10.
The AI features are optional. They run either on the managed NetLock AI reached through the Members Portal, or on an OpenAI-compatible provider the deployment configures and hosts itself; the choice is made under Settings → AI / LLM (see A.11.2).
Two kinds exist: the general-purpose AI Chat page, and targeted per-feature assistants. The targeted integrations are the AI Assistant in the Scripts editor (which writes directly into a script), the AI Assistant on the Automations dialogs, the AI SQL Assistant in the Widget Editor, and the Analyze with AI action on event and audit details (which opens AI Chat with the entry pre-filled). See Chapter 13.
A separate, optional Customer AI feature extends AI to end users: when enabled in the tray-icon policy, staff open an AI chat directly from the agent's tray icon. The conversation history is encrypted on the device with the user's password and stored encrypted; operators cannot read it. To answer, each message is passed through the NetLock server to the configured model. Accounts self-register and are activated by an operator (or auto-activated per tenant), and usage is bounded by per-user and per-tenant monthly token limits. Operators manage these accounts from the Customer AI dialog on the Tenants pages, gated by the enduser_ai_accounts permission. See Chapter 13.6.
Whitelabeling options
Whitelabeling is broad enough to list separately. Each option below is configured under Settings → Whitelabeling and documented in A.6.
| Option | Summary |
|---|---|
| Console title and logo | Custom title text and a custom logo image. |
| Login page layout | Centred-card or side-panel layout with toggles for logo, glow, and fun facts. |
| Login page background | Custom background image or video. |
| Welcome text and footer links | Custom greeting and custom footer links on the login page. |
| AppBar and navigation | Per-icon AppBar visibility and a collapsed-drawer mode. |
| Visual effects | Optional seasonal overlays and particle backgrounds. |
| Colour palette | A full light-mode and dark-mode colour palette with live preview. |
| Iframe embedding | Allows or blocks embedding the Console in third-party applications. |
| Theme import, export, and community themes | JSON theme exchange and a community theme gallery. |
X.7.2 Server features
The server is the central service the Console reads from and agents report to. Self-hosted operators run it themselves; cloud operators do not.
| Feature | Summary | Documented in |
|---|---|---|
| Role-based deployment | The backend can be split into separate server roles. | A.1 |
| Agent handshake | Agents need the package key of one of your installers; new devices wait for approval unless the installer authorizes them automatically. | A.1 |
Self-hosted only: Server architecture and role splitting apply to self-hosted deployments. Cloud deployments delegate server operation to the hosted operations team.
X.7.3 Device management and remote access
These features act on managed devices through the agent. Platform columns record where each is available.
| Feature | Win | Linux | macOS |
|---|---|---|---|
| CPU, RAM, network, and drive inventory | Yes | Yes | Yes |
| Installed software inventory | Yes | Yes | Yes |
| Service overview | Yes | Yes | Yes |
| Logon, Task Scheduler, and driver overview | Yes | — | — |
| Remote Task Manager | Yes | Yes | Yes |
| Remote Service Manager | Yes | Yes | Yes |
| Remote Shell | PowerShell | Bash | Zsh |
| Bulk Remote Shell | Yes | Yes | Yes |
| Remote File Browser | Yes | Yes | Yes |
| Remote Event Log Viewer | Yes | — | — |
| Remote Registry Editor | Yes | — | — |
| Remote Screen Control | Yes | Yes (Wayland, see X.8.5) | Yes (agent 3.3.0.11 and later) |
| Audio call to the signed-in user (from the end user chat) | Yes | — | — |
| Streaming modes (Quality / Balanced / Performance / Auto / Custom) | Yes | Frame rate and resolution only | Yes (agent 3.3.0.11 and later) |
| Paste files into a screen session | Yes (agent 3.3.0.11 and later) | GNOME and KDE on Wayland; without wl-clipboard saved to Downloads (agent 3.3.0.11 and later) | Yes (agent 3.3.0.11 and later) |
| SNMP Tools | Yes | Yes | Yes |
| Uninstall application | Yes | Yes | Yes |
| Wake on LAN | Yes | Yes | Yes |
| Relay Server | Yes | Yes | Yes |
Remote Screen Control streams the device's screen as JPEG frames from the agent through the NetLock server to the viewer (the web Console, the Relay App or the NetLock app). The product does not use VNC or RDP.
The picture is tuned per session with a stream mode: Quality (4:4:4 colour, native resolution, up to 20 fps), Balanced (the default, up to 30 fps), Performance (up to 60 fps), Auto (adapts to the connection) and Custom; a statistics overlay shows frame rate, bandwidth, latency and the capture method in use. Full detail, including session switching, recording, and unattended access, is in Chapter 3 and A.7; the modes are described in A.7.5.
On Linux a mode sets the frame-rate cap and the resolution ceiling only. Remote Screen Control runs in the device's Wayland session; its prerequisites, the desktop support matrix, and how unattended access works on Wayland are covered in X.8.5.
Files can be pasted into a running session from the web Console and the Relay App: dropped onto the picture, pressed in with Ctrl+V or chosen with Send files, up to 100 files and 10 GB per transfer. The device puts them on its clipboard and pastes them where the user works; it needs devices_remote_file_browser and the 3.3.0.11 agent. See A.7.10.
Viewers
| Feature | Web Console | Relay App | NetLock app |
|---|---|---|---|
| Windows, Linux and macOS devices | Yes | Yes | Yes |
| Stream modes, advanced settings, statistics | Yes | Yes | Yes |
| Zoom and full screen | Yes | Yes (F11; Esc goes to the device) | Pinch zoom |
| Recording indicator, start and stop | Yes | Yes | Yes |
| Hint about another technician on the device | Yes | Yes | Yes |
| View of the remote clipboard | Yes | Yes | Yes |
| Paste files | Yes | Yes | No |
| Touchpad mode | — | — | Yes |
| Anchored devices (endpoint protection) | Yes | Yes, approval in the NetLock app | Yes |
| Android devices: view and control the screen | Yes | — | — |
Android phones and tablets are viewed and, when their policy allows it, controlled from the web console: taps, swipes, scrolling, the system buttons and, from Android 13, text; the user agrees on the phone for every session. See A.7.12 and X.8.7.
Sessions from the Relay App and the NetLock app run under the account that owns the relay key: that account's name is shown in the consent prompt on the device and written to the audit log. See A.7.9.
The Relay Server provides TCP tunnels and jump-host access for network devices without an agent. The Relay App and NetMesh links use end-to-end encrypted TCP tunnels. Relay Web Access is encrypted between the browser and the server. See Chapter 9.
X.7.4 Security and control
| Feature | Win | Linux | macOS | Notes |
|---|---|---|---|---|
| Microsoft Defender management | Yes | No | No | Scan jobs, exclusions, and notifications. |
| Firewall status | Yes | Yes | Yes | Read-only inventory of firewall state. |
| Firewall configuration | Yes | Yes | No | Windows uses Defender Firewall; Linux uses UFW. |
| Application Control | Yes | No | No | Allowlist rulesets matched by path, metadata, hash, or signing certificate. |
| USB Device Control | Yes | No | No | Allowlist with device, tenant, location, group, and global scope. |
Antivirus management covers Microsoft Defender only; third-party antivirus products are not managed. Application Control and Device Control are library features under Collections (see Chapter 8.6 and Chapter 8.7). A ruleset or whitelist reaches devices only through a policy; see Chapter 6.
X.7.5 Software and patching
| Feature | Win | Linux | macOS | Notes |
|---|---|---|---|---|
| App Hub catalogue | Winget, Chocolatey, Script | Flathub, Script | Script | Catalogue only; not an execution engine. |
| Software Deployment | Yes | Yes | Yes | Four-step wizard with retry and per-device attempt tracking. |
| Patch Management | Yes | Yes | Yes | Windows: OS, Winget, Chocolatey. Linux: Apt, Dnf, Yum. macOS: native. Docker: image updates (Linux with Docker Engine only). |
The App Hub is a catalogue you pick from; installation runs through Software Deployment. See Chapter 8.5 and Chapter 8.8.
Patch Management is split across two places. The /patch-management page is a global approval queue with compliance and SLA tracking; per-policy rollout rules (schedule, deployment rings, reboot, retry, notifications) live inside the policy editor. See Chapter 7 for the page and Chapter 6 for per-policy rollout.
X.7.6 Automation and monitoring
| Feature | Win | Linux | macOS | Notes |
|---|---|---|---|---|
| Policies | Yes | Yes | Yes | One policy per device; agent behaviour, security, patching, App Hub. |
| Automations | Yes | Yes | Yes | Routes one policy to devices by a device-attribute condition. |
| Jobs | Yes | Yes | Yes | Scheduled script execution with twelve schedule types. |
| Sensors | Yes | Yes | Yes | Utilization, event log, script, service, ping, and SNMP sensors. |
| Device uptime monitoring | Yes | Yes | Yes | Connection and disconnection alerts per device. |
| Website uptime monitoring | Yes | Yes | Yes | HTTP status, SSL expiry, response time, content checks. |
| Port Scanner | Yes | Yes | Yes | TCP scans of operator-defined targets with banner grabbing. |
An automation is a conditions → policy and/or items rule. It has no event triggers or schedules, and its only actions are assigning one policy and adding sensors and jobs from the library. Every rule has a priority; among the rules whose conditions all hold for a device, the one with the lowest number that assigns a policy decides the policy, and the sensors and jobs of every matching rule are added on top. Automations cannot run scripts themselves or send notifications. See Chapter 5 for the resolution model and Chapter 6 for what a policy contains.
Note: A device is assigned at most one policy at a time. Policies do not attach to tenants, locations, groups, or devices directly; they are routed through Automations.
Besides alerting, sensors can run an action script on a threshold breach. Sensor and Job mechanics live in Chapter 8.2 and Chapter 8.3. Website uptime monitoring and the Port Scanner are documented in Chapter 9.
Tray icon
The agent exposes an optional tray application to end users on all three platforms. Its branding, button set, App Hub window labels, AI Chat and the chat request to the administrators are configured per policy.
| Feature | Win | Linux | macOS |
|---|---|---|---|
| User tray icon | Yes | Yes | Yes |
| Custom tray branding | Yes | Yes | Yes |
| App Hub window | Yes | Yes | Yes |
| AI Chat (end user) | Yes | Yes | Yes |
| Chat request to the administrators (end user) | Yes | Yes | Yes |
| Incoming audio call window (end user) | Yes | — | — |
On macOS the tray icon, and with it the consent prompt and the support badge of Remote Screen Control, the end user chat and the chat request, need agent 3.3.0.11 or later. The macOS prerequisites are in X.8.6.
The tray AI Chat is optional. The conversation history is encrypted on the device with the user's password and stored encrypted; operators cannot read it. To answer, each message is passed through the NetLock server to the configured model. It is enabled and fully labelled per policy and managed from the Console's Customer AI dialog; see Chapter 13.6.
When the policy allows it, an end user can ask the administrators for a chat from the tray menu. The request is offered to the administrators who are signed in to the web console, hold the End user chat permission and have access to the device's tenant. The first who accepts gets the end user chat of the device with the user's session pre-selected. If no such administrator is signed in, the user is told right away that nobody is available. See §6.5.
An operator can also call the signed-in user of a Windows device from the end user chat: the tray icon shows an incoming call window with the operator's name and picture, and after accepting the user talks through the default microphone and playback device, with device pickers, mute, echo suppression and hang up in the same window. The call needs the Audio call permission (devices_remote_audio_call), the Allow audio calls switch of the policy and a browser with WebCodecs (Chrome, Edge, Firefox 130+, Safari 26+); calls are not recorded. See A.7.7.
See Chapter 6 for tray-icon policy settings.
X.7.7 Platform support
The supported operating systems and architectures, further platforms the agent runs on, and the Linux prerequisites for Remote Screen Control on Wayland are documented on their own page: Platform Support.
Related chapters
- Chapter 3 — Devices — device inventory and remote access.
- Chapter 5 — Automations — policy routing.
- Chapter 6 — Policies — what a policy configures.
- Chapter 7 — Patch Management — the approval queue.
- Chapter 8 — Collections — the reusable libraries.
- Chapter 9 — File Server & Monitoring — relay, uptime, port scanning.
- X.5 — Integration endpoints — external systems the product talks to.
- X.8 — Platform Support — supported operating systems and Linux Remote Screen Control prerequisites.
Changelog pointer
Where to find release notes: the changelog on the NetLock website and the update notice in the Console.
Platform Support
The operating systems and architectures the agent supports, further platforms the agent runs on, and the prerequisites for Remote Screen Control on Linux (Wayland) and macOS, and what Android devices support.