Asset types and device mapping

Settings > Documentation holds the two screens that configure the asset side of MSPControl’s documentation features.

Screen	Purpose
Asset Types	The categories assets can belong to, and the fields each carries
Asset Device Mapping	Links asset records to the managed devices they describe

Settings > Documentation is not the documentation itself

This group configures asset handling. The documentation content — notes, passwords, certificates and photos — lives in the space-scoped Documentation menu, not here.

The two groups share a name and contain entirely different things, which is a reliable source of confusion.

Asset types

An asset type defines a category — server, switch, printer, licence — and what is recorded against it. Types are defined once at platform level and used by every customer’s documentation.

Decide the fields before the estate fills up

Adding a field to an asset type later leaves every existing asset of that type blank for it, and back-filling is manual. Spending time on the field list before technicians start creating assets is cheaper than retrofitting.

Asset device mapping

Links an asset record to the managed device it describes, so documentation and live device data refer to the same machine.

Without a mapping the two exist side by side and drift: the asset record says one thing, the device details another, and nobody knows which is current.

Unmapped assets are the ones that go stale

An asset that is not mapped to a device is maintained entirely by hand. Those are the records still describing a machine that was replaced two years ago.

Where an asset corresponds to a managed device, map it — the mapping is what keeps the documentation honest without anyone maintaining it.

Related

• Documentation assets
• Device details