Properties overview
Areas, buildings, floors, rooms, beds, services and assets — the structure every other record points at.
How the structure nests
The portfolio is a hierarchy. Each level exists so you can report and assign permissions at that level later.
| Level | Created in | What depends on it |
|---|---|---|
| Area | Settings → Operations setup → Areas | Grouping buildings for reports |
| Building | Properties → Buildings | Staff permissions, default services, payment accounts |
| Floor | Settings → Operations setup → Floors | Room ordering and the property layout |
| Room | Properties → Rooms | Leases, invoices, meters, assets |
| Bed | Properties → Beds | Per-bed leases in shared rooms |
Create them in this order. A room cannot be created without a building and a floor, and a lease cannot be signed without a room.
What attaches to a room
- Services priced for that room — see Services.
- Meters for electricity and water — see Meters.
- Assets handed over with the room — see Assets.
- Leases, and through them tenants, invoices and deposits.
Because everything hangs off the room, renaming a room is safe but deleting one is not. Deactivate instead of deleting when a room goes out of service.
Do you need beds?
| You rent | Use | Why |
|---|---|---|
| The whole room to one lease | Rooms only | A bed layer adds a required field to every lease and invoice |
| Places in a shared room, signed separately | Rooms + beds | Each bed carries its own lease, invoice and occupancy |
Once a room has active beds, the bed field becomes required on leases, reservations, invoices and bookings for that room. Decide before you start signing.
Last updated