KW Knowledge base

Assets

The Assets module is the register for *physical things* you track — laptops, monitors, switches, printers, network gear, anything physical — beyond what RMM covers. It's separate from RMM because most assets aren't reachable over the networ

Mitch Wigham
Updated 24 June 2026 · 7 views

12 · Assets

The Assets module is the register for physical things you track — laptops, monitors, switches, printers, network gear, anything physical — beyond what RMM covers. It's separate from RMM because most assets aren't reachable over the network or don't run an agent.

Where to find it

Sidebar → Assets or /assets. Requires the assets feature.

Concepts

  • Asset — a single physical item with a tag, category, location, status, and an optional assignee.
  • Category — type of asset, with an optional auto-numbered tag scheme. E.g. LAPTOP-0001, LAPTOP-0002, …
  • Location — free-text field naming where the asset physically lives. (A separate curated location list exists under Admin → Asset locations; the current create/edit forms still capture location as free text.)
  • Assignee — the employee an asset is checked out to. Assets can also be scoped to a department. An asset may additionally carry a customerId (auto-populated when it was created from an RMM device enrolment), though the portal create/edit forms don't expose a customer picker.

Layout

+--------------------------------------------------------------+
| KPIs: Total · In use · In stock · Repair · Retired · Lost    |
|       Warranty < 30d                                         |
|--------------------------------------------------------------|
| [All][In use][In stock][Repair][Retired][Lost]  Cat ▾ Dept ▾ |
|                                          [search…]           |
|--------------------------------------------------------------|
| Tag        Asset        Category  Status  Assigned  Location |
| LAPTOP-42  Dell XPS 13  Laptops   In use  Mitch     London   |
| DESK-0014  Standing desk Desks    In use  —         Office   |
| NET-0008   Cisco SG250  Network   In use  —         Server   |
+--------------------------------------------------------------+

📷 Screenshot placeholder: screenshots/assets-list.png

Asset detail

+----------------------------------------------------------+
| 💻 Dell XPS 13            [↗ Check out] [Edit] [Delete]  |
|  [In use] [LAPTOP-0042] [RMM · LON-LAP-12]               |
|----------------------------------------------------------|
| Serial  ABC123        Asset tag  LAPTOP-0042             |
| Category Laptops      Location   London HQ               |
| Purchase 2024-04-12   Warranty   2027-04-12              |
| Cost    £1,200.00     Assigned   Mitch · Engineer        |
+----------------------------------------------------------+
| Details (edit panel)        | History            [+ note]|
+----------------------------------------------------------+

📷 Screenshot placeholder: screenshots/asset-detail.png

The detail page is a summary card, then a two-column layout: an Details edit panel on the left and a History timeline on the right. There are no separate tabs.

Linkage

If the asset is an RMM-managed endpoint it carries an rmmDeviceId link, shown as an "RMM · hostname" badge on the detail page. The link is populated automatically when an asset is created from an RMM device enrolment — there is no manual "link to device" picker in the asset UI.

Creating an asset

The create form is a three-step wizard:

  1. + New asset.
  2. Scope — confirm the organisation and optionally pick a department (or skip to add an unassigned asset).
  3. Device — fill in the details: name (required), category, status, serial, asset tag, manufacturer, model, location, cost, purchase date, warranty end, notes.
  4. Assign — optionally pick an employee to assign the asset to. Picking one is captured on the record; leave blank to add it unassigned.
  5. Create asset.

If you leave the asset tag blank and the chosen category has a tag scheme, the tag is auto-minted from the category counter. You can also type a tag manually.

Asset tags

Tag scheme is configured per category by an admin under Admin → Asset categories. A category's tag scheme is optional — categories without a prefix don't auto-number. When set, it comprises:

  • Prefix — e.g. LAPTOP (upper-case A–Z0–9, 2–16 chars)
  • Padding18 digits → 0001, 0002, …
  • Next number — starts at the category's "Start at" value (default 1) and increments

⚠️ Caution. Tag numbers are monotonic and never reused. If you delete LAPTOP-0042, the next new asset gets LAPTOP-0043. This is intentional so old asset stickers always resolve to a known asset. Once a category has issued its first tag, its prefix can no longer be changed; the padding can only be changed while the counter is still at its starting value.

Locations

In the asset create and edit forms, Location is a free-text field — type the site or room directly (e.g. London HQ — Server room).

A separate curated location list is maintained under Admin → Asset locations for reporting purposes, but the current asset forms do not offer a location dropdown.

Status

Statuses are a fixed set:

  • In use — assigned to a person / in service
  • In stock — in stockroom, not deployed (default for new assets)
  • Repair — out for repair
  • Retired — end of life
  • Lost — reported missing

The status set is fixed in code; there is no admin screen to add custom statuses.

History

Every asset has a History timeline (right-hand panel on the detail page) that records, with timestamps:

  • Created — when the asset was added
  • Updated — generic detail edits
  • Status changed — shows the old → new status
  • Checked out / Checked in — with the employee involved
  • Note added — free-text notes you type in the panel

You add a note straight from the History panel using the inline "Add a note…" box.

Bulk operations

The asset list does not currently support multi-select bulk actions or label printing. Edit assets one at a time from their detail page.

Search

The list search box matches asset name, serial, asset tag, manufacturer, and model. It combines with the status, category, and department filters.

Common workflows

Onboard a new laptop

  1. Receive from supplier.
  2. + New asset → Device step: Category Laptops, Status In stock, Location "stockroom".
  3. Create → if the category has a tag scheme the tag is minted (LAPTOP-0043).
  4. When deployed, open the asset → ↗ Check out → pick the staff member. This sets the status to In use and records the check-out in History. Edit the Location to their office.

Find a missing asset

  • /assets → filter Status = Lost → open the asset → see the History timeline.

Permissions

All asset endpoints require an authenticated session. The asset service does not enforce per-role restrictions — any signed-in user with the assets feature can view, create, edit, check assets in/out, and delete them. The category and location admin screens live under /admin and are reached through the admin area.

See also

Still need help?

Log a support ticket and the team will pick it up from this page.