Finding your way around the console

The console is organised by the question you are trying to answer rather than by the subsystem that answers it, which occasionally means the same record is reachable from several places. That is intentional.

The dashboards are the top layer. The RMM dashboard is the technician view: what is online, what is failing, what needs attention today. The executive dashboard is the management view: estate size, compliance position, risk. The MSP business-intelligence dashboard is the commercial view: leakage, contract position, client risk. If you are new, spend your first week in the RMM dashboard and ignore the other two.

Endpoints is the operational core. Every enrolled machine, filterable by client, site and state. From an individual endpoint you can reach its inventory, patch position, health history, action log, and the remote terminal.

Assets is broader than Endpoints and answers ownership questions rather than operational ones — who has this, what is it worth, when does the warranty expire, what happened to it. The per-asset timeline is the most underused view in the product; it answers "what changed on this machine and when" without reconstructing the story from tickets.

Tickets, recurring issues and problems sit together. A recurring issue is detected across ticket history; if it turns out to be a real underlying fault rather than a coincidence, you promote it to a tracked problem record.

Compliance, security findings, vulnerabilities and the risk register form the evidence layer. Reports and Exports sit downstream of all of it.

Global search cuts across everything. It covers endpoints, assets, clients, tickets and documentation from one box, and it is almost always faster than navigating. If you find yourself clicking through three levels of a client tree to reach a machine you already know the name of, use search instead.