#product docs

Nine pages, written in the order you will need them. Every one carries a Limits section stating plainly what that capability does not do, because finding out later is worse.

Start here

If you have fifteen minutes and administrator rights on one machine, the quickstart will get you to a status board you can read. Everything else makes more sense afterwards.

##getting started

QuickstartAgent installed, inbox connected, first status in 15 minutes.

##core

HelpdeskEmail and WhatsApp intake, auto-sorting, suggested fixes.Device inventoryHardware, installed software, warranty, who has what.Licence trackingSeats against installs, renewals, unused seats flagged.PatchingPatch inventory, critical flags, approval-based rollout.

##workflows

Joiners and leaversChecklists that create accounts, assign kit, revoke access.Service providersOne board across every client you look after.

##reference

Agent permissionsRead-only by default. What the agent can never do.

##conventions

Prerequisites at the top of a page are genuinely required, not recommended.
Code blocks show the command and, underneath, the output you should expect. If your output differs, stop there rather than carrying on.
Limits sections are exhaustive for the capability they describe. If something is not listed as a limit, it works.
Panels framed like a terminal are the dashboard's own output, shown as the command line renders it.

Open the quickstart Ask us something instead