Assets & Inventory

Assignments & history

Assignments & history

Ownership in lazyit is not a field you overwrite — it is a record of who held an asset and when. This is what keeps the asset the first-class citizen: people rotate, assets persist, and the full ownership trail is kept automatically. You manage owners from an asset’s detail page, in the Owners panel of its side column.

Assigning an owner

Open an asset, go to Owners, and choose Assign user. Pick the person and add an optional note (for example “primary work laptop”). The asset now lists that person as an active owner.

A few things to know:

  • An asset can have several owners at once. lazyit supports concurrent, shared ownership — for example a server that several people are responsible for. Assigning a second owner does not displace the first.
  • One active assignment per person per asset. You can’t assign the same person to the same asset twice while the first assignment is still active — release it first.
  • You can only assign a live asset to a live user — deactivated assets and users can’t be given new assignments.

Releasing an owner

To end someone’s ownership, choose Release next to that owner. Releasing one owner does not affect the others. You can add a note explaining why (for example a return or a handover).

Releasing does not delete the assignment — it stamps it with a release time and moves it into the ownership history. This is deliberate: there is no “delete assignment” action, because the point is to keep the record. To move an asset from one person to another, release the old owner and assign the new one.

An owner who has left the company still appears as an active owner until you explicitly release the assignment — lazyit never silently drops ownership records.

Acknowledging receipt

Assigning an asset records who is accountable for it — but it doesn’t prove the person actually received it. Acknowledge receipt closes that gap: the owner themselves confirms they took possession.

  • Self-service. Only the owner can acknowledge their own active assignment. Open the asset, find yourself under Owners, and choose Acknowledge receipt. You can add an optional note (for example “received in good condition”). No one can acknowledge on someone else’s behalf.
  • A confirmed date. Once acknowledged, the owner’s line shows Acknowledged <date> and the event is written to the asset’s activity log. Until then it reads Awaiting acknowledgement, so an operator can see at a glance which handovers are still unconfirmed.
  • The assigner is notified. When you acknowledge, whoever assigned the asset to you gets a notification (in their bell, and by email unless they’ve opted out) — a quiet, automatic confirmation that the handover is complete.
  • Set once. Acknowledgement is a one-way confirmation: it can’t be undone or repeated, and an assignment that has already been acknowledged or released can’t be acknowledged again.

This is optional — an assignment is valid whether or not it’s ever acknowledged — but for asset handovers where accountability matters, it gives you a clean record that the person confirmed receipt.

Quick actions from the assets list

You don’t have to open an asset to manage its owner. Each row on the Assets list carries one colored quick action:

  • Assign (blue) on a row with no owner — opens the same picker as the detail page.
  • Unassign (amber) on a row that already has one — asks you to confirm, then releases the current owner into the ownership history.

Each row also has a … menu with the rest: open the asset in a new tab, edit or clone it, assign or remove its assignment, change status (a quick submenu), and delete. Changing status from here is instant and reversible — no confirmation, just like the bulk action. These shortcuts respect your permissions: you only see the actions you’re allowed to run.

Activity and ownership history

Every asset carries an append-only activity log — a timeline of discrete events, newest first. The log is immutable: entries are written, never edited or deleted. You’ll find it on the asset detail page in the Activity tab, with the ownership-specific entries under Ownership history in the same tab.

Recorded events include:

  • Created and Deleted / Restored — the asset’s lifecycle.
  • Status changes — for example Operational → In maintenance.
  • Location and Model changes.
  • Specs changes — edits to custom fields.
  • Updated — edits to the asset’s other details (name, serial, tag, notes, company, dates, cost); the entry lists which fields were edited — for example Changed: Name, Notes — never their old or new values, and marks an edit that came from a re-import via re-import. Entries recorded before this list existed read Details updated. The edit also shows in Reports.
  • Assigned and Released — ownership changes, naming the owner involved.
  • Acknowledged — an owner confirmed receipt of the asset checked out to them.
  • Consumable delivered and Consumable returned — supplies fitted to or left in the asset (a toner in a printer, a spare disk in a server), with the quantity and a link to the consumable; and units of a returnable item given back. See Stock movements.

Each entry records what changed, when, and by whom (or “System” when lazyit acted on its own). Together with soft delete everywhere, this gives you the audit trail of an asset’s whole life without any extra bookkeeping.

Consumables delivered to the asset

An asset’s page has a Consumables delivered section: every consumable delivered to this asset, newest first, with the quantity and when. A returnable item shows what is still outstanding and offers Return…; Deliver consumable records a new delivery to the asset without leaving the page. Both need permission to record stock movements. The section is hidden if you cannot view consumables. See Stock movements.

What’s next