Clients, Sites & Endpoint Inventory

Operators organize work under a client company and a site, then enroll machines like acme-wks-01. Inventory is how you know what you are connecting to before you open Remote Console.

First hierarchy (Acme)

On Clients:

Create client Acme Corp (or your real customer / internal org).
Add site Acme HQ.
Assign enrolled endpoints to that client and site.
Confirm the new client appears in the header scope switcher.

The same operator → company → site → computer pattern fits MSPs, internal IT, and small teams. Azure / Graph onboarding is optional and is not required to finish this first step.

Installer bootstrap can also stamp a client and site on new registrations so acme-wks-01 lands in the right place without a later reassignment.

Endpoints table

Open Environment or the Endpoints table. Typical columns:

Status: online, degraded, offline unexpected, or off expected (a clean shutdown is not an incident).
Hostname: current name from inventory (the monitor identity stays stable if the name changes).
Client and site: where the machine sits in the book.
OS: Windows, macOS, or Linux.
Agent version and last heartbeat.

Search covers hostnames, client/site names, and installed application names. The Software tab rolls up unique applications in the current scope. That is observe-only inventory, not the Packages catalog used to deploy software.

Vitals before you connect

Select an endpoint to read live vitals the agent reports: CPU, memory, and disk usage, plus remote-session health such as capture failures or registration errors. Use that picture before you open Remote Console so you are not guessing whether the machine can take a session.

Software and hardware snapshots refresh on a timer. For Dell, HP, HPE, and Lenovo, warranty lookup uses the device serial and opens the vendor page. FlowRMM does not invent start/end dates.

Environment graph

The Environment canvas is the same neighborhood as the table, drawn as client → sites → computers. Health stays in the halo color. Signed-in people, pinned runbooks, linked knowledge, recent operator activity, and alerts attach to the machines they belong to.

This is enrollment plus the monitor poll plus stored knowledge links. It is not a discovered LAN, and it does not invent SNMP neighbors or website visitors. Empty neighborhoods invite a pin; they do not fabricate a fleet map.

Hover a device to see only what it touches. Inspect a node for the play log on that computer.

Related guides

Want hands-on help evaluating Cohort 01? Book a demo or apply for Cohort 01.