Appearance
Assets
Your asset register is your live RMM fleet.
No second database. No reconciliation script. Every agent reporting in is a row in your asset register, ready to be categorised, tagged, contract-bound and billed.
- One source of truth
Live agent rows are the asset rows. No sync job, no reconciliation script, no spreadsheet drift.
- Asset → invoice
Recurring invoice run counts billable assets per contract. Quantity snapshot stored on the line.
- Categorise + filter
Tags, billing categories, custom fields per organisation. Saved views for the operations team.
How it works
One source of truth.
- Agents register on first connect. Each agent becomes an asset row tied to its client / organisation / location.
- Add billing category, contract binding, and tags from the SPA.
- The asset is now eligible for the next recurring invoice run.
- If an agent goes offline, the asset stays — billing categories handle deactivated-but-historically-billed cleanly.
Billing flow
Asset count → invoice line, automatic.
- Recurring invoice run counts billable assets per contract
- Quantity snapshot stored on the invoice line for audit
- Proration rules applied for mid-cycle changes
- Voiding an invoice releases CDRs, reverses credits, rolls back recurring periods, and marks the QBO invoice for void or credit note
Documentation overlay
Structured in-product documentation is queued so asset rows can carry runbooks, password vault references, network diagrams and KB articles natively — not via a separate tool to license and keep in sync.
Pairs well with
Other things in the platform
Common questions
Can I add non-agent assets?
Yes. Manual asset rows for printers, switches, network gear are supported. They participate in billing the same way agent-backed assets do.What happens when an agent uninstalls?
The asset is marked offline. Billing categories handle whether to continue billing (e.g., archived seat) or stop (e.g., decommissioned).Can I bulk-edit assets?
Yes. Multi-select, bulk tag, bulk billing-category change.Will documentation merge with assets?
That is the plan. Structured in-product documentation lands on asset rows once the documentation pillar ships.