Skip to main content
An asset is anything Docusnap365 holds in the inventory — scanned or created by hand. Its type determines which fields and which detail page it has.

​
Inventory and Organization

Inventory

The technical assets from the scan — servers, network devices, databases, cloud services.

Organization

What you create by hand — departments, processes, people, applications and information.
Types and their families are listed under Data Captured.

​
Origin

An asset comes into being in three ways: through a scan, by hand, or through import.
A scan module can represent a device twice: as a system component of the computer it belongs to, and at the same time as an asset of its own with type Monitor — for example when scanning with Windows (AD), Windows (IP), Linux or macOS.

​
Relationships and other modules

Relations connect assets with each other and give the inventory its meaning. See Relationships. Other modules also attach to an asset: ITAM for lifecycle, ownership, warranty and cost, ISMS for protection needs and risk, and CVE Analysis for known vulnerabilities. All three appear as their own tab on the detail page; what they show is described in their own module. For evaluation and bulk work, use the lists — see Lists and Filters.

​
Limits

Without a scan, a manual entry or an import, an asset does not exist in the inventory — Docusnap365 only knows what it has captured or what someone has created. Which fields and which detail page an asset has is determined by its type; you define your own fields and a detail tab for your types under Data Model. Getting started with the first assets is covered in Importing Assets from a Spreadsheet. How to create, edit and delete individual assets is described in Create assets and Edit and delete assets.