Properties is the spine of Orveya — a self-referencing tree that runs from portfolio to building to lot, tenancy and asset. Every other register hangs off it, so every record knows exactly where it sits.
Buildings are not flat. A portfolio holds towers, a tower holds lots and tenancies, a tenancy holds the assets that serve it. Properties models that hierarchy as a single self-referencing tree, so every record in Orveya knows exactly where it sits — and one click walks you up or down the structure.
Counts roll up automatically — lots, tenancies and floor area at every level — so you always know the real shape of what you manage. AI address verification keeps the tree clean as you grow, checking each new property against a known address before it lands.
A single self-referencing structure: a portfolio holds buildings, a building holds lots, tenancies and common areas, and each of those holds the assets that serve it. Every record links to a node, so context flows from one place.
When you add a property, Theo checks it against a known address record before it is saved, so duplicates and typos do not pollute the tree as you grow.
As deep as your real estate. A portfolio can hold buildings, a building can hold lots, tenancies and common areas, and each of those can hold the assets that serve it.
Yes. Tickets, assets, tenants, contractors and compliance all attach to a node in the tree, so context flows from one place rather than being re-keyed in each module.