Your RMM knows a laptop’s operating system, memory, storage, and current status. Your documentation explains who the laptop belongs to, which client it supports, and where to find the procedure for rebuilding it.
A technician needs both views. Weavestream’s Level RMM integration puts inventory facts into client asset records and keeps the RMM detail nearby, so looking up a device also leads to its documentation.
Map Level Groups to Clients
The integration uses one Level account and a read-only API key. Each top-level Level group maps to a Weavestream company, and devices in nested groups follow their top-level group into that company.
This makes the group structure worth reviewing before the first sync. Devices outside every group are not synced. A successful connection check confirms the key can see the account; it does not prove you have mapped each group to the right client.
Weavestream includes credential instructions and Check setup in the integration. The Level RMM guide covers the complete connection and mapping process.
Use Your Existing Asset Layouts
On Map layouts, choose where Level devices should go and which fields should receive their standard facts. Hostname, manufacturer, model, operating system, CPU, RAM, storage, MAC address, IP address, and role can fill your layout fields.
You can select a suitable field, create one, or choose Don’t sync for a fact you do not want. This lets an established Workstations layout remain the place your technicians document computers.
The first sync writes the mapped values, including when it adopts an existing asset. Review those mappings before importing: a field included in the initial mapping is a field you have chosen to populate from Level.
Match Before Creating Another Laptop
A device with a serial number can join an existing asset when exactly one eligible record matches. Matching ignores letter case. Ambiguous matches are reported instead of being linked by guesswork.
An adopted asset keeps the name your team gave it. An asset created by Level follows the source’s device name. Devices without serial numbers, including some virtual machines, cannot match existing assets by serial number; new records remain linked to their Level device IDs for later syncs.
Supported integrations can also share an asset. For example, the same laptop from Level and Microsoft Intune can appear as one asset with separate provider sections. This depends on an eligible, unique match; it is not a promise that every duplicate inventory record will merge automatically.
Keep RMM Detail Close to the Documentation
The Level RMM section includes reported status, storage usage by partition, network interfaces, security information, available patches, and active alerts. It also holds hardware detail, tags, and Level notes.
Those details are a synchronized view, not a replacement for Level’s live console. Patches and alerts depend on the account’s access, and the integration does not provide installed software, agent versions, or warranty dates. Your purchase and warranty documentation still has a job to do.
The section is internal and is not shown to client users.
Review Differences Instead of Losing Edits
After the initial sync, mapped values continue following Level while they still match the last value it wrote. If a technician changes a field in Weavestream and Level disagrees, the integration surfaces a difference rather than overwriting the edit.
Your team can choose Use Level RMM value or Keep ours, either on the asset or from the integration’s Differences tab. Those choices require asset-edit permission and are audited.
Start with a dry run, inspect Run history, and then check a few devices after the first real sync. The Level RMM setup guide explains the field and matching rules; Weavestream’s product overview shows how those assets connect to the rest of your documentation.