Storage floor plan software: the site is not a spreadsheet.

A unit list answers administrative questions, but it does not show how the site works physically. Staff still need to know which building, floor, zone or aisle holds a unit, how spaces relate to entrances and circulation, and what the cluster of occupied or available units looks like on the ground.

The map models buildings and floors, accepts an uploaded blueprint and calibrates it against real dimensions, then lets an authorised editor draw the operational layout over the top. Drawn objects link to units. The structural symbols cover the landmarks people actually navigate by: walls, doors, entrances, lifts, stairs and roller shutters.

• Create a building, floor and zone hierarchy rather than one undifferentiated canvas.
• Upload and calibrate an existing blueprint as a drawing reference.
• Draw, move and edit unit geometry alongside structural symbols.
• Link each drawn space to the authoritative unit inventory record.
• Publish a reviewed layout, hold drafts back, and roll back a change that was wrong.

A static plan is out of date the moment occupancy changes. Because each drawn object links to a unit, the map expresses current status rather than a colour somebody stored last quarter. Staff scan for available, occupied, reserved or attention-needing spaces and move straight into the unit workflow.

Search is spatial as well as textual: find a unit and the view pans to its position. In view mode, hover detail supports quick inspection and a drawer carries the next level of context. Dragging or panning deliberately does not behave like a trailing click on a unit, which is exactly the kind of thing that compiles correctly and still makes a map unusable under touch.

That matters during tours, arrivals, maintenance and collections work. The interface answers where is it alongside what state is it in, rather than asking staff to translate row B-114 out of a table into a physical route.

Only a role allowed to see it anywhere else. Unit detail is fetched through an authorised server action, facility scope is applied before anything is returned, and tenant fields are redacted when the staff member lacks the capability.

This is the rule the whole platform uses: permission is enforced per column, not per page. A drawn object identifies a record; it does not grant the right to read every field behind that record. The boundary moved to the column after the site map was found returning tenant names, balances and document counts to anyone who could open it, and the per-role behaviour is now pinned by its own test file so it cannot drift back.

Editing is separated from the published operational view. You can work on geometry, calibration and symbols without every intermediate movement reaching daily users. Publishing is then a deliberate act, and rollback is the recovery path when a later layout turns out to be worse than the one it replaced.

Geometry and editor behaviour carry dedicated tests for measurement, calibration, snapping, inspection, symbols, viewport transforms, blueprint handling and store operations, with end-to-end coverage of the inventory map in a browser. A map can compile perfectly and still be misleading under a real pointer, which is why the coverage sits at that level.

Into the work. A selected unit leads to unit administration and, where permitted, to the customer and rental behind it. Inventory state is moved by reservations, move-ins, transfers and move-outs, and the arrears process creates much of the work staff then need to understand in physical context: which units in this block are locked out, and where they are.

What the map does not do is open a door. Tenant door credentials, an access-event feed and per-site access windows exist elsewhere in the platform, but selecting a unit on the canvas does not provision, suspend or restore physical access, and no badge on a drawing should be read as though it could.

The operator map is not the public booking map. It is tied to the management console, and it should not be read as a promise that a customer picks a precise unit off the same canvas at checkout. The public booking journey works from bookable unit types, live availability and pricing, then allocates the rental against the unit it held. A public map would need its own privacy, availability and conversion rules, and those do not exist.

Column gating is a limit as well as a protection. Some roles will open the map, see every unit and its status, and never see a balance or a tenant contact. If your intention is that a front-desk role can read a balance off the floor plan, that is a permission decision to take deliberately, not something the map grants by being open.