Module configuration
Asset
Register, use and write off company assets — laptops, screens, vehicles, software licences. One place for the whole life cycle, linked to owner and location.
Updated May 18, 2026
Configuration · Modules · 4.6
The Asset module manages your company assets: laptops, screens, vehicles, software licences — anything you want to know what it is, where it sits, who has it, and what its status is. Under the hood assets are configuration items of class “Asset”, but you manage them through a dedicated list with asset-specific actions.
Why this matters to the business
"Who has which laptop?"
Asset detail shows owner, issue date and history. No more Excel hunts when IT changes happen.
"Licences expire without warning"
Expiry date + notification rule → ticket created automatically 30 days in advance.
"Asset broken → who gets the ticket?"
Ticket on an asset routes via CI type and workgroup — no manual triage needed.
"Write-off and reuse unmanaged"
Statuses (In use · Stock · Repair · Written off) show the real life cycle per asset.
What sets an Asset apart from a regular CI?
Assets are configuration items of class “Asset” (see 4.2). What the module adds:
Owner assignment
One or more users linked as the actual user — with history on handover.
Status life cycle
Predefined statuses the asset passes through — feeds reporting and routing.
List actions
Bulk actions: issue, take back, change status — works on multiple assets at once.
Standard fields
| Field | What it's for |
|---|---|
| Template | Drives which fields are visible (see 4.2). One template per asset type — laptop, monitor, licence. |
| Identification | Name, serial number, asset tag, barcode. One or more — depends on the type. |
| Owner / user | Primary user(s). Distinction between lender (owner) and borrower (user). |
| Location | Physical location. For mobile assets: office location of the user. |
| Status | In use · Stock · Repair · Lost · Written off (configurable per type). |
| Purchase date & price | For depreciation and chargeback; feeds the finance link. |
| Warranty / end date | Trigger for automatic notifications for replacement or renewal. |
| Parent / child | Licence sits under laptop; keyboard under workstation set. |
Which decisions will you make?
Which asset types do you manage here?
Limit your scope. Hardware and software licences are standard; furniture often overkill.
Who creates assets?
Centrally by procurement (consistent) or decentrally by admins (fast). With or without an approval step.
Which statuses count in reporting?
Stock assets not in occupancy metrics; written-off assets out of the "active count" filter.
Warranty and expiry policy
Notification X days ahead, ticket to whom? Procurement, IT asset manager or the user themselves?