Skip to content

Client mapping

Every device Ledger sees belongs to exactly one source (one of the tools you connected, such as your RMM, EDR, Microsoft or PSA connections) and needs to be attributed to one of your clients before the device matrix, exceptions, and billing reconciliation can reason about it correctly. An unmapped device still shows up — flagged with the NO_CLIENT_MAPPING exception — but every source-specific column reads "Not applicable" (shown as a dash) until it's mapped, since Ledger has no client scope to compare against.

Mapping during onboarding

The getting-started wizard's client-mapping step lists the organizations from your connected sources and suggests one of your existing Ledger clients for each when the names match exactly or are close enough by fuzzy matching. Each suggestion shows a confidence percentage; confirm them one at a time, or use "Confirm all suggestions" to accept every suggested pair in one click. An organization with no matching client shows "no suggestion": create the client from the Client mapping screen (below), then map it. A new account starts with no Ledger clients, so expect to create them there.

Mapping any time, per connection

Beyond onboarding, the Client mapping screen (reachable from any connection's detail page) shows two lists side by side: the source's own organizations/sites, and your Ledger clients. It auto-suggests a mapping wherever an org's name and a client's name match exactly once both are lowercased — you don't have to accept the suggestion, and nothing is mapped without your action.

For each source organization you can:

  • Map it to an existing Ledger client.
  • Create client — creates a new Ledger client from the organization's name and maps it in the same step, for an org that has no existing match at all.
  • Unmap — clears a mapping you no longer want, without deleting the client itself.

What mapping actually changes

A mapping ties one source's external organization/site identifier to one Ledger client. From that point on, every device your sync pulls in from that organization resolves to that client automatically — nothing needs re-mapping on future syncs unless the org itself is renamed or replaced on the source side.