Quickstart

1. Create the site

An operator provisions the customer site. This mints two credentials and shows each once:

• an enrollment token (cen_…) — short-lived, limited-use, for installing agents
• a status token (cst_…) — read-only, for the customer’s status page and weekly report

2. Enroll workstations

Run the install command on each machine that uses QuickBooks — including the machine that hosts the company file. The installer carries only the enrollment token; the agent exchanges it on first contact for its own per-device credential.

That matters: a leaked installer burns one device, not the whole site, and any single machine can be revoked on its own.

3. Set the update policy

Choose per organisation:

• observe — report the build, change nothing.
• lock — hold the org on a pinned release and alert on drift. Recommended for accounting environments, where a surprise change mid-close is worse than being one build behind.

4. Watch

• Console — every site and endpoint, health at a glance, drill into any machine.
• Status page — a read-only view for the customer.
• Weekly report — a branded digest, emailed.

What you should see in week one

Real environments almost always surface something on the first pass — a workstation stuck at 100 Mbps, a fleet spread across several maintenance builds, or a default printer that will eventually take QuickBooks down. That first report is usually the one that pays for the tool.