Overdue rent, maintenance triage, and lease expiries — asked in plain English.
Your leasing, rent-roll, and maintenance systems already track every unit, payment, and work order. Knodox reads them read-only and turns them into permission-aware answers — scoped by portfolio and department, with tenant income, credit, and ID masked before the model reads a row.
For portfolio managers, leasing, maintenance, and accounting.
Rent, leases, and work orders live across systems that only get queried at month-end. The questions that protect NOI — overdue rent, maintenance risk, expiring leases — go unasked between reports.
A missed payment on one unit is easy to overlook across hundreds. Which leases are past due, and by how much, should be one question — not a spreadsheet.
An urgent pest issue and a routine touch-up look the same in a work-order list. Triage by priority and status shouldn't require reading every ticket.
Income, credit score, and ID numbers can't reach a model for a role that shouldn't see them — and one portfolio's data can't leak into another.
Example answers on a representative multi-portfolio dataset. Every figure is derived from the underlying lease, payment, and work-order rows and checked back against the source before it's shown.
"Which leases have overdue payments?"
One lease is past due in this portfolio: $2,300 in rent unpaid on Riverside Heights #101 — with the unit, tenant, and due date attached, so it's ready to chase, not just count. The rest of the rent roll is current.
Traced to the payments table"Show me this unit's file."
Same question. Different roles. Different views — enforced at the data layer:
"Summarise maintenance requests by priority and status?"
Two high-priority requests need attention — an HVAC unit in progress and an electrical fault still open — alongside routine and scheduled items. Ranked by priority and status so nothing urgent waits behind a touch-up.
Derived from maintenance_requestsThe same three guarantees that run across all of Knodox — applied to property data.
Roles map from your identity provider; every query is scoped by portfolio and department at retrieval. Tenant income, credit, and ID are masked before the model reads a row for roles without clearance.
Rent, balances, and occupancy are checked back against the source rows. If a figure can't be traced, it's flagged — not shown. No invented arrears.
Pin any answer — overdue rent, maintenance by priority, leases expiring soon — into a living dashboard that refreshes against your data, scoped to each viewer's role.
Point your teams at Knodox's Ask interface, or keep your own property portal and call Knodox's permission-aware retrieval API. Either way, the same portfolio and department rules apply per user.
Managers and staff log in and ask directly. Connect a read-only source, map roles, and go.
Keep your own owner or resident portal and call the retrieval API with the end-user's identity on every request. Knodox mints a scoped token and returns only what they're allowed to see.
Income, credit score, ID, and contact details are masked before the model reads them — unless the caller's role is explicitly cleared.
Thirty minutes. We connect a read-only copy of one of your sources, set up two roles, and let you ask your first real question. No demo data, no slideware.