Key Concepts
These are the objects and terms the console uses. They recur across every module, so it is worth reading this page before the rest of the guide.
Each entry is the platform’s own term, with what it means in practice.
Who and what you manage
| Column | Description |
| Customer | An organisation whose devices and tickets you manage. Every device, ticket and discovery belongs to a customer. The console can be filtered to one customer or left on 'All Customers'. |
| Device | A managed endpoint — a desktop, laptop or server carrying the communication client. Devices appear in Assets and can be acted on singly or in groups. |
| Device group | A named set of devices inside a customer. Policies and actions are usually applied to a group rather than to devices one at a time. |
| Network device | A device found by a network discovery that carries no client of its own — a printer, router, switch or similar. It is watched indirectly, through a probe device. |
| Probe device | A managed device that scans the network and runs checks on behalf of the devices that have no client. |
What runs on them
| Column | Description |
| Communication client | The agent installed on an endpoint when it is enrolled. It is what lets the console see the device and act on it. |
| Client security | The security software deployed to an endpoint alongside the communication client: antivirus, firewall, containment and the rest. |
| Policy / configuration profile | The bundle of settings applied to a device. A policy carries the security settings, the monitors the device runs and the procedures it runs on a schedule. The console labels this both as a policy and as a profile; they are the same object. |
| Procedure | A script, an operating-system patch job or a third-party patch job that runs on a device. Procedures are written once, approved, then run on demand or on a schedule through a policy. |
| Monitor | A condition watched on a device — disk filling up, a service stopped, a web page changed. When the condition is met the monitor raises an alert, and can run a procedure to fix the problem. |
| Condition | The individual test inside a monitor. A monitor can hold several, and be set to fire when all of them or any one of them is met. |
| Alert | What a monitor raises when its conditions are met. An alert names who is emailed and can open a ticket. |
When things may happen
| Column | Description |
| Maintenance window | A period during which disruptive work may be done on a device. Outside the window the platform warns you, or refuses outright, depending on how the window is configured. |
| Schedule | When a procedure or a discovery runs by itself. Procedure schedules live in policies; discovery schedules live on the discovery. |
Finding and fixing
| Column | Description |
| Discovery | A saved scan that finds the devices on a network, by address range or by reading a directory. |
| Blueprint | A set of SNMP rules that recognises a kind of network device and classifies it when a discovery meets it. |
| Patch | An update for the operating system or for an installed application. Patches are approved or declined, then installed. |
| Ticket | A unit of support work. Tickets arrive from users, from integrations, or from the platform itself when an alert fires. |
| SLA | The response and resolution targets a ticket is measured against. |
Note: a policy is the thing that connects the rest: it is how a monitor, a procedure or a security setting actually reaches a device. An object that is not referenced by any policy does nothing, however it is configured.
See Best Practices for the order in which to set these up.
