Properties

Properties

A property is one bookable unit — typically an apartment or flat. Everything the system does for a reservation reads from the property's configuration: address (for the guidebook), check-in window (for task scheduling), Nuki locks (for PIN generation), default pricing (for the revenue simulation).

In this section


Where it lives

The property list is at /properties. Click any row to open that property's full configuration page.

Property list

Property Manager (the bulk editor) is at /property-manager — see Property Configuration for when to use which.


Lifecycle

  1. Create a property — usually triggered automatically when a new listing syncs from Hospitable. Properties created via Hospitable webhook have basic data populated; the rest is filled in by an admin.
  2. Complete the configuration — address, photos, check-in window, Nuki lock IDs, pricing inputs. See Property Configuration.
  3. Assign teammates — at least one host and one cleaner. Without an assignee, tasks for this property have no one to route to.
  4. Activate the smart lock — link the Nuki account, register lock IDs. See Smart Locks.
  5. Receive reservations — Hospitable webhook → reservation created → task templates fire.

Common questions

  • A property is missing its name in a task notification — see #137. The most common cause is the property record was created from a webhook that didn't include the name; populate it in the property editor.
  • Check-in time on a reservation is wrong — reservations can override the property default via earlyCheckinTime / lateCheckoutTime. The reservation-level value always wins. See Reservations.
  • Smart lock has no PIN generated for today's guest — the per-stay PIN is generated by the Generate access code task. If it's blocked or the canonical guest row is wrong, see #260 and Reservations → Send Check-in.
Source: the FlatsBratislava operator manual.