ENES
Assets & Inventory

Asset basics

Asset basics

An asset is a single thing your team owns and is accountable for — a laptop, a server, a switch, a monitor, a license. In lazyit the asset is the first-class record: people come and go, but the asset stays, and its whole history travels with it. You manage assets from the Assets area.

Registering an asset

Open Assets and choose New asset. The form captures:

  • Name — required, your own label for the unit (for example Ada's laptop or SW-CORE-01). lazyit does not enforce a naming convention; pick one that suits your team.
  • Status — required (see below).
  • Model — optional. Link the asset to an asset model (its make/model). Picking a model can pre-fill custom fields from the model’s defaults.
  • Location — optional. Where the unit physically lives. See Locations.
  • Serial and Asset tag — both optional (see Serial and asset tag below).
  • Company — optional grouping label (see Company below).
  • Purchase date and Warranty end — optional dates.
  • Notes and Custom fields — optional free-form detail.

You do not assign an owner here. Ownership is a separate step you take once the asset exists — see Assignments & history.

Status

Every asset is classified by a status — there is no default, so you choose one when you register it. The values are:

  • Operational — in active service.
  • In maintenance — temporarily out for repair or servicing.
  • In storage — kept in stock, not currently in use.
  • Retired — decommissioned, kept for the record.
  • Lost — unaccounted for.
  • Unknown — status not established.

Status appears as a colored badge in the list and on the detail page. Changing it is recorded in the asset’s activity log. You can also set the status of several assets at once from the list.

Serial and asset tag

These are two different things, and both are optional:

  • Serial — the manufacturer’s serial number of the physical unit.
  • Asset tag — your own company label, the one you write on the sticker (for example LZ-0001).

Each is unique among live assets when set: if you try to save a serial or asset tag that another live asset already uses, lazyit refuses it. When an asset is deactivated, its serial and asset tag are freed, so the value can be reused or restored later.

The asset tag is not the asset’s internal identity — lazyit keeps a separate, permanent internal id for links and references. The asset tag is a human-facing label you can change at any time. If you want lazyit to assign asset tags automatically from a running number, see Asset tags.

Company

Company is an optional grouping label on an asset — a way to tag which organization, business unit or client an asset belongs to (handy if you manage gear for several clients, or split kit by legal entity). It is only for grouping, filtering and reporting: it is not an access control. Company does not hide anything — anyone who can see assets sees all assets regardless of their company; setting it simply lets you narrow the list to one company when you want to.

It is a free-text field with autocomplete: as you type, lazyit suggests companies you’ve already used on other assets, so you reuse the same spelling instead of creating near-duplicates — but you can always type a brand-new value. There is no separate “companies” screen to manage: a company exists simply because at least one asset uses it.

On the asset detail page the company is shown when set, and links to the list filtered by that company. You can filter and add a Company column to the list (see below).

Custom fields

Different kinds of asset carry different attributes — a laptop has RAM and a CPU, a switch has a port count and an IP. Rather than force a fixed set of columns, lazyit stores these as custom fields: a free-form list of name/value pairs on the asset (for example ram → 16GB, ip → 10.0.0.4).

Add, edit or remove rows in the Custom fields section of the form. When you pick a model that has default specs, those values are copied in as a starting point — you can change them for this individual unit before saving. Custom fields are shown as a tidy label/value list on the detail page.

Finding assets in the list

The Assets list has a search box and a Status dropdown right in the toolbar, plus a Filters button that opens a small panel for the rest:

  • Category and Location — narrow to one model category or one place.
  • Company — narrow to one company (the grouping label above). Only companies in use appear.
  • Owner — show only the assets currently assigned to a specific person. Start typing a name to pick them; the list then shows just that person’s live assignments.
  • Ownership — filter by whether an asset has any current owner at all (Has owners / No owners), regardless of who.

The Filters button shows a small count of how many of these are active. Every filter you set also appears as a removable chip below the toolbar, and the filters live in the page address, so a filtered view is easy to undo, share or bookmark.

Choosing which columns to show

The Columns button (next to Filters) opens a checklist of the table’s columns — asset tag, model, category, location, company, status, owners and updated. Untick the ones you don’t care about to slim the table down to what matters for you. The Name column and the row actions always stay. Your choice is remembered in this browser, so the table keeps the same shape next time you visit. (This governs the desktop table; the mobile card view always shows the full set.)

Assets on the topology map

If an asset backs a node on the Infrastructure diagram — for example a host, a NAS or a switch you’ve placed on the map — its detail page shows an On topology badge next to the status, and the same marker appears as a small share glyph beside the asset’s name in the list. A View in topology button on the detail page jumps straight to the map, flying to that node and giving it a brief highlight so you can spot which one it is at a glance. (You only see these when you have permission to view the topology.) The reverse link exists too: a node’s details panel links its inventory name back to this asset, so you can move between an asset and its node in either direction.

Editing, cloning and deactivating

  • Edit updates the asset in place; each meaningful change (status, location, model, custom fields) is written to the activity log.
  • Clone opens a new asset pre-filled from this one, with the serial and asset tag cleared so the copy gets its own — handy for registering a batch of identical units.
  • Deactivating an asset is a soft delete: the record is hidden from the normal list but never destroyed, so its history is preserved. Deactivated assets can be restored by an administrator, which also reclaims their freed serial and asset tag (unless a live asset has taken the value meanwhile). lazyit never hard-deletes asset data.

What’s next