Locations

A location is where an asset physically lives — an office, a datacenter, a rack, a warehouse, or “remote / with an employee”. Locations answer half of the core inventory question: not just what do we have, but where is it. You manage them from the Locations area.

Adding a location

Open Locations and create a new one. A location has:

• Name — required.
• Type — required; every location is classified (see below).
• Parent location — optional; nests this location under another (see Nesting locations).
• Description, Address, Floor and Notes — all optional free text.

Floor is a label, not a number — values like “Ground”, “Basement 1” or “Mezzanine” are fine.

Location types

Each location is classified by a type, chosen from a fixed set:

• Office
• Datacenter
• Rack
• Remote — for assets that aren’t at a fixed site (for example a laptop out with an employee).
• Storage
• Other

Nesting locations

Locations can be nested to mirror how your estate is really laid out — a datacenter contains racks, a site contains rooms, and so on. Set a location’s Parent location to hang it under another; leave it as top-level for a standalone site. A location with no parent is a root.

On a location’s page, a breadcrumb shows its full ancestry (for example Datacenter → Rack A3), and each ancestor links to its own page. On an asset, the location field shows the full path, not just the leaf, so you can see at a glance that a server lives in HQ → DC1 → Rack A3.

You can re-parent a location at any time by editing it and changing its parent, or promote it back to top-level by choosing None (top-level). A location cannot be nested under itself or under one of its own descendants (that would create a loop) — lazyit rejects such a move and explains why on the form. Nesting is optional: a flat list still works if you don’t need the structure.

Assigning a location to an asset

You set an asset’s location on the asset form — it is one of the optional fields when you register or edit an asset. See Asset basics. A location is optional: an asset can exist without one.

Changing an asset’s location is recorded in that asset’s activity log, so you can see when a unit moved.

The “assets here” view

Open a location to see its details together with the assets currently at that location — the inventory physically located there. This is the quick answer to “what’s in this rack?” or “what’s at the branch office?”.

Removing a location

Locations are soft-deleted, never destroyed. Removing a location does not delete the assets that point to it — those assets simply become location-less for that link, and the record is kept for history. lazyit favors auditability over strict tidiness.

What’s next

• Asset basics — register units and set their location.
• Models & categories — classify what the asset is.