Managing properties
Add the complex, building, and unit, open the property profile, and send every request to the right place.
A property in Nabeeh is the place where maintenance happens: a complex, a building, a floor, or a unit. Every maintenance request needs a clear property so the service provider reaches the right door.
List, then profile
On the Properties list, use the search bar to find a property by name or contact number and choose its classification from the horizontal strip. The Filters button holds customer, floor-plan, and unit-type options, plus the branch filter when you are viewing all branches. Active filters appear below the classification strip; remove one directly or choose Clear all. The list and child properties (floors and units) are ordered by name. A selected branch shows properties homed there and properties shared with it. A shared property shows its home branch plus +N or Shared. Open a card to go to the property profile.
Use the view switch at the top of the page to change between Card view and Table view; your choice is remembered on this browser. The table uses the same search, classification strip, and Filters, and adds columns for classification, customer, location, branch (when viewing all branches), sub-properties, active maintenance requests, and date added. Select a property name or the menu button to open its actions, and select the Sub-properties count to browse floors and units without leaving the list.
The profile holds the address, child properties, linked customers, assets on that place, and earlier maintenance requests. Do not invent a unit from memory; open the property first if you are unsure.
Build the tree from the top down
- Add the parent property (complex or building) with the name and address the team will recognize.
- Add child properties under it: a building in a complex, a floor, or a unit.
- Check the hierarchy list so each unit sits under the right building.
- Link a customer to the unit when they are a standing occupant; otherwise their name is entered on the request form.
If you move a unit to another building, change the parent on the profile. Do not delete and recreate the unit — old requests and QR codes stay on the same record.
If the place is on the wrong branch, use Move to branch on the profile. Child properties, assets, floor plans, and open requests follow. Completed and canceled requests stay unless you ask to move history too. The same record keeps its QR codes. A move that would leave a maintenance contract covering two branches is blocked. If the place is already shared, you can check Make exclusive to the destination branch to drop the extra shares.
If two teams both work the same campus, use Share with branch instead of cloning. Home stays put. The extra branch sees the same property, QR codes, and history. Child properties and assets keep their own shares unless you check Also share child properties and assets. You cannot stop sharing the home branch. To stop sharing one extra branch — or every extra branch — open Share with branch again and dismiss that chip. The home chip has no ×. The button stays on the profile even after every assigned branch already sees the place.
Tip: Staff assigned to only one branch do not see Move to branch or Share with branch. Staff who are not assigned to the place’s home branch also do not see Share with branch.
Access code
Each property can carry an Access Code — a built-in field on the create and edit form, not a custom field. Turn on Show property access code in account settings to show the field; when off, saved values stay in the database but the field is hidden on forms. Use it for gate codes, keypad numbers, or entry instructions the team needs on site.
Tip: Name the unit the way the resident sees it on the door. An internal label that does not match the plate sends teams to the wrong request.
Bulk import
When you have dozens of units, use import from the list: download the template, fill the rows, review the batch, then submit. The template has an optional branch column — leave it empty to use the header branch (or Main); a named value files that row even if the header is elsewhere. Updating an existing property with a different branch in that column moves its home there and keeps extra shares. Older files without the column still import. Fix a bad row inside the batch before you submit. Do not upload a file of real mobile numbers for a trial; use the demo account.
Archive
Archive a property that the account no longer operates, if archive is available, instead of deleting it. An archived property leaves everyday pickers and stays on the archived list when you need the history; open that list from View Archived Properties at the bottom of the Filter properties panel (opened from Filters). The public QR picker still shows only active places. Tracking a request by reference can still find it after the unit is archived.
After properties are in place, generate a QR code from the profile or a bulk export, then register assets on units that need equipment work rather than building-only work.
What to read next
- QR codes — generate from the profile or a batch export after units are ready.
- Assets — register equipment on units that need machine work.
- Customers — link a permanent occupant to the unit.
- Branches — select the branch before you create a request or print a code; move or share a place from the profile.
- Budgets — cap and track utility spend on a building or unit.
- Custom fields — add an extra field, such as an internal reference, to a property's edit form.