Skip to content

Getting started

An account is created for your MSP by the Ledger team, who send a sign-in invitation by email. You sign in through the hosted sign-in page. After you first sign in, you land on an onboarding wizard that walks you from connecting your first source to your first insight. You can also reach every one of these screens directly at any time — the wizard is a guided shortcut, not the only way in.

The two-source rule

The wizard asks you to connect two sources. Ledger's whole value is reconciling what two-or-more tools say about the same device, so a single connected source can't yet show you a meaningful exception — the wizard's "next" button on steps 1 and 2 stays disabled until a connection has actually been saved on that step, so you can't skip past this by accident.

Step 1 — Connect your first source

Pick any one of NinjaOne, Microsoft Intune, Huntress, SentinelOne, ConnectWise PSA, ConnectWise Automate, Datto RMM, Microsoft Defender, HaloPSA, or Autotask and connect it. Each has its own credential walkthrough:

Ledger tests the connection as soon as you save it and shows the result on the connection; "next" unlocks once the connection is saved (fix a failed test from the Connections screen before moving on).

Step 2 — Connect your second source

Same as step 1, with a different source. This is what makes reconciliation possible — a device an RMM has never heard of but an EDR sees, or vice versa, is exactly the kind of gap Ledger exists to surface.

Step 3 — Map your clients

Ledger lists the organizations from your two sources and suggests one of your existing Ledger clients for each when the names match closely enough, with a confidence score next to each suggestion. A new account has no Ledger clients yet; for an organization showing "no suggestion", create the client from the Client mapping screen first. Confirm suggestions one at a time, or use "Confirm all suggestions" to accept every one in a single click. See client mapping for the full picture, including how to add mappings by hand later.

Step 4 — First sync

Ledger triggers a sync of both connections right away and shows live progress. Once both finish, it immediately runs device reconciliation straight away, so you don't wait around.

Step 5 — First insight

You land on the exceptions summary with a banner telling you what was found — "We found N exceptions across M devices" — and a link into the full exceptions list. From here on, Ledger keeps syncing and re-evaluating on its own schedule; nothing further is required to keep the picture current.

Where to go next

  • Add more sources any time — the wizard's two-source minimum is a starting point, not a ceiling.
  • Review the device matrix for a per-device, per-source view.
  • If you bill clients per device, read billing reconciliation to understand how Ledger links agreements to devices (and when it honestly can't).
  • Set up a recurring scheduled report so this picture lands in an inbox on its own.