Core Concepts
The vocabulary NetLock RMM is built on: agents, tenants, policies, Collections, and permissions.
Core Concepts
NetLock RMM is easier to learn if you read the vocabulary first. The product uses a small number of terms very consistently, and almost every chapter in Part II assumes you already understand the ones introduced here.
The agent, the server, and the Console
Three components form the system:
- The agent is a small piece of software installed on every device you want to manage. It reports status, runs jobs you schedule, enforces policies, and provides the endpoint for remote shells and file transfers. Once installed it talks to the server on a regular schedule.
- The server is the central component. It holds configuration, receives data from agents, runs the web Console, and mediates remote-access sessions. In cloud deployments the vendor runs it; in self-hosted deployments you run it.
- The Console is the browser-based user interface you spend your day in. It reads and writes configuration to the server; it does not talk to agents directly.
In every feature, the Console tells the server what should happen, and the agent carries it out.
Tenant, location, group
NetLock RMM organises managed devices into a three-level hierarchy. Every device belongs to exactly one group, which belongs to exactly one location, which belongs to exactly one tenant.
- A tenant is the top-level container. For an in-house IT team this usually maps to "the company". For an MSP it maps to one customer organisation.
- A location is a subdivision of a tenant, usually a physical site or office. A small tenant might have one location; a multi-site customer will have several.
- A group is a subdivision of a location. Groups typically reflect how devices should be configured rather than where they physically are, for example
Servers,Workstations,Kiosks.
The hierarchy is primarily an organisational structure for devices and for scoping what users can see. Policies are not attached directly to a tenant, location, or group. Instead, they are routed to devices by Automations, which match devices by attributes such as their tenant, location, or group name.
See Chapter 4 for the full reference on managing this hierarchy.
Tip: Group devices by how they should be configured, not just where they live. "Every laptop, regardless of site" is a better group than "every device in the Berlin office" if your policies differ primarily by device type.
Agents and devices
A device is a managed computer: a workstation, laptop, or server. When you install the agent on a new device, it contacts the server and registers itself as an unauthorized device: present on the network, but not yet accepted into a tenant. An administrator reviews unauthorized devices in Devices → Unauthorized, chooses the tenant, location, and group to assign them to, and approves them. From that moment the device is an authorized device and appears in the main device list.
Note: A device that does not appear in the device list is usually waiting for approval. The First-Run Walkthrough covers the approval flow in detail.
Devices also carry a label (a free-form human-readable name), custom fields defined at the Collections level, and any number of per-device settings. Chapter 3 is the canonical reference for everything device-related.
Policies
A policy is a named bundle of desired configuration for a device. Examples: "managed laptops (strict)", "kiosk devices", "server baseline". A single policy can configure:
- General agent behaviour (sync interval, auto-update).
- Tray Icon branding and visibility.
- Windows Defender Antivirus (exclusions, scan jobs, notifications).
- Windows Application Control and USB Device Control rulesets.
- Linux UFW firewall.
- SNMP sensors to collect on devices.
- Scheduled Jobs to run on devices.
- Patch Management rollout rules, per platform (Windows, Linux, macOS, Docker).
- Which App Hub apps are exposed in the Tray Icon.
Policies are edited in the Policy Settings page and stored in the server database. The agent picks up changes on its next sync (5-1440 min, configurable per policy).
Important: NetLock RMM does not keep a policy version history and does not support rolling back to a previous policy state. Edits apply in place. If you need a safety net, clone a policy before making a risky change.
A device is assigned at most one policy at a time. Policies are not layered or merged.
Automations
In NetLock RMM, an automation is a rule that decides which policy gets assigned to which device, and which sensors and jobs a device gets on top of that policy, based on a list of conditions:
IF all of these conditions hold for a device THEN assign policy <name> and/or add sensors and jobsA condition compares one fact of the device: the device itself, its tenant, location or group, its internal IP address or domain, its platform, a device attribute such as the device name, the operating system or the label compared with an operator (equals, contains, starts with, wildcard pattern, regular expression), a service or an installed application of its inventory, or a custom field value. A rule has at least one condition, all of them have to hold, and any of them can be negated. Every rule has a priority number and an enabled switch.
An automation has no event, schedule, or manual trigger. Its only actions are assigning a policy and adding sensors and jobs (see Chapter 5.6). It does not run scripts itself, send notifications, create tickets, or chain steps; it routes policies, sensors, and jobs to devices.
When a device syncs, the server takes the enabled rules whose conditions all hold for the device, orders them by priority (the lower number wins), then by the number of conditions (more first), then by age (older first), and assigns the policy of the first one. If no rule matches, the device receives the default policy when one is marked on the Policies page; otherwise it has no policy. The dialog proposes a priority from the rule's most specific organisation condition (device 100, internal IP 200, domain 300, group 400, location 500, tenant 600, otherwise 700), so a rule for one device beats a rule for its group, which beats a rule for its tenant, unless you choose otherwise. Adding, editing, enabling, disabling, or deleting an automation forces the affected devices to re-evaluate immediately.
To give devices a policy, you need both a Policy and at least one Automation whose condition matches those devices. A policy without a matching automation is not applied to any device. The exception is the default policy: marked on the Policies page, it covers every device that no automation reaches.
For event-driven work, such as "run a script when a disk fills up" or "open a ticket when a sensor breaches a threshold", NetLock RMM uses Sensors (with action scripts) and Jobs (scheduled scripts), not Automations. See Chapter 8 — Collections.
Collections
Collections is the umbrella term for reusable building blocks you create once and reference from many places. Eight kinds of Collection item exist:
| Item | Purpose |
|---|---|
| Script | A PowerShell or Bash snippet you run on one or many devices. |
| Job | A scheduled background task that runs on the agent. |
| Sensor | A custom metric the agent reports back on an interval, such as CPU, memory, or a specific application's health. |
| Custom Field | A per-device attribute (text, dropdown, date, checkbox) added to every device inventory. |
| App Hub entry | A packaged application from Winget (Windows) or Flathub (Linux), or a manual package, available for deployment. |
| Application Control ruleset | Rules that whitelist applications by hash or path. |
| Device Control entry | Rules that whitelist USB and peripheral devices. |
| Software Deployment | A packaged deployment of one or more App Hub entries or manual packages to a target set of devices. |
Collections items are cross-referenced: an automation may add jobs and sensors that run scripts, a policy may include an Application Control ruleset, a software deployment may use App Hub entries. Chapter 8 documents each in detail.
Permissions
NetLock RMM uses a role-based permissions model. Each user holds a set of permission flags that gate access to Console features. The common flag shapes are:
*_enabled: whether the user sees the feature at all (for examplecollections_enabled).*_add: whether the user can create new items in the feature.*_manage: whether the user can open existing items; saving and deleting take*_editand*_delete.
Permission flags control which items appear in the navigation menu on the left and which buttons are visible on a page. A user without dashboard_enabled will not see the Dashboard menu item; a user with collections_application_control_enabled but without collections_application_control_edit can open rulesets but not save changes.
Permission names appear throughout this manual in backticks, for example collections_application_control_manage. See Users & Roles for how to assemble permissions into roles, and the Permission reference appendix for a full list.
Real-time updates
Several parts of the Console update in real time using a persistent connection to the server. Device status, script and job execution results, and policy deployment notifications all flow in without a page refresh.
What to read next
- First-Run Walkthrough — apply these concepts to a fresh deployment.
- Navigating the Console — where each concept lives in the UI.
- Glossary — one-line definitions for quick lookup.