Weavestream
Start Self-Hosting View on GitHub
4 min read

One Asset, Several Integrations: Keep the Context Without Losing Your Edits

How Weavestream matches supported integration records to existing assets, prioritizes provider values, and surfaces differences when synced data disagrees with your team's edits.

integrationsasset-managementdata-qualitymspit-documentation
01 / Post4 min read · 677 words

A laptop appears in your RMM and in Microsoft Intune. A person exists in Google Workspace and Microsoft 365. Your team has already documented each of them in Weavestream.

Importing every source into a fresh record gives you more inventory rows, but it can make the documentation harder to use. Which laptop should hold the repair notes? Which person should be linked to the onboarding procedure? And which source should win when they report different values?

Weavestream’s newer integration model gives supported providers a way to share an asset and makes disagreements visible.

Start With a Reliable Match

Level RMM, Google Workspace, and Microsoft 365 can match records to existing assets using fields such as a device serial number or a person’s email address.

Matching ignores letter case, but requires exactly one eligible match. If several assets match, Weavestream reports the ambiguity and leaves them unlinked. It does not assume that an exact-case match makes the other candidates irrelevant.

Supported providers can also join an asset another supported integration already syncs. A laptop reported by both Level and Intune can then have one asset page, with a separate section showing each provider’s details.

This behavior does not apply to every driver. Assets from Action1, NinjaOne, UniFi, and Breeze are not shared through this mechanism. Check the integration documentation for the provider and resource you plan to use.

Choose the Fields You Want to Sync

The Map layouts tab lets you select a destination layout and match field, then choose where supported standard facts should go. You can use an existing field, create a suitable one, or leave a fact out with Don’t sync.

The first sync writes the mapped values, including for an existing asset it adopts. Review those mappings before importing. Preserving later manual edits does not mean an initial import leaves every mapped value untouched.

Afterward, a field still holding the integration’s last-written value follows the source. Empty fields can be filled. When someone changes a field in Weavestream, a different upstream value is surfaced for review instead of silently replacing that edit.

Decide Which Provider Leads

Under Admin → Settings → Integrations, an administrator can set the integration priority order. For each standard field, the highest-priority provider with a value leads; lower-priority providers can fill gaps and report differing values in their own sections.

For a laptop documented by both Level and Intune, you might prefer Level’s hardware facts while keeping Intune’s compliance and enrollment information in its provider section. One asset can hold both contexts without treating every provider-specific detail as a competing field.

Priority changes take effect on subsequent syncs. They preserve manual edits and recorded choices, and saving the order requires reauthentication and is audited. Domain matching follows its own rules and is not controlled by this asset priority order.

Resolve Differences Deliberately

Differences appear on the asset and on the integration’s Differences tab, where your team can review them across companies.

Use the source value accepts the provider’s value. Keep ours retains the Weavestream value and stops flagging that disagreement until the source value changes again. Resolutions need permission to edit the asset and are recorded in the audit log.

Choosing a lower-priority provider’s value is an explicit decision for that field. If you want that provider to lead consistently, change the priority order rather than repeatedly resolving the same type of disagreement.

Keep Provider Detail and Client Sharing Separate

Integration sections are internal and are never shown to client users. Their values are not searchable yet. Mapped fields remain part of the normal asset layout and follow that layout’s visibility settings, so review those settings when choosing fields to populate.

A useful first rollout is small: select a client, check serial numbers or email addresses, review the field mappings, and inspect a dry run. After the first real sync, check for duplicate records and differences before expanding to more clients.

The result is documentation with a clear place for source data and human judgment. Explore the supported integrations and read the matching and priority rules before connecting overlapping sources.

02 / Keep reading

Latest from the blog