Who uses it
Four portals, four audiences, and how to tell which one you want.
There are four separate surfaces, and they are genuinely separate — a resident cannot see the dashboard, and a housekeeper signed into the dashboard sees only their own work.
| Portal | Who | What they do there |
|---|---|---|
| Dashboard | Operators and office staff, including housekeeping and maintenance staff | Everything, narrowed by role: catalogue, reservations, rent, move-outs, cleaning, maintenance, messaging, analytics — a field-staff account sees only its own cleaning events, errands and maintenance jobs |
| Resident portal | People living in a unit, and applicants | Review and sign a contract, pay rent, register guests, report problems, give notice |
| Owner portal | Building owners | Monthly statements, who is in their units, occupancy |
| Contractor link | External contractors | One job, through an unguessable link, with no account at all |
A fifth surface is not a portal: guests on short stays check in through a tokenised link and read a handbook, without ever signing in.
The dashboard
Where the business is run. Everything else in this documentation's platform guide describes a dashboard screen.
Staff roles narrow the dashboard rather than opening a different one. A housekeeper-role account signing into the dashboard is redirected to their own cleaning events and timesheets and cannot reach any money page. See Roles and portals.
The resident portal
A resident's whole relationship with the tenancy: the contract to review and sign, rent to pay, receipts, registering an overnight guest, reporting a problem, and filing a move-out notice.
Applicants use it before they are residents — the contract review step happens here, before anyone has moved in.
A resident sees their own tenancy and nothing else. Not the building's other residents, not their charges, not their contact details. That boundary is the main reason the portal exists as its own surface rather than as a filtered view of the dashboard.
The owner portal
Owners see their own buildings: monthly statements, occupancy, and who is in their units.
They do not see resident contact details. An owner asking why they cannot message a resident directly is hitting a deliberate boundary, not a gap — the operator sits between the two on purpose.
An owner who also lives in one of their units is a different thing again: they occupy it, but it is not an ordinary tenancy. See Availability.
Housekeeping and maintenance staff
Cleaning and maintenance staff sign in at the same dashboard as everyone else, narrowed to their role: today's cleaning events, the room checks to complete, errands, and (for maintenance staff) their maintenance jobs and the hours worked. They cannot reach other staff's data or any money page.
Contractor links
An external contractor gets no account. They receive a link to one maintenance project, which is writable: they can log hours, add a purchase, and move tasks along.
That link also exposes the building handbook, including entrance codes and WiFi. Treat it as a building credential, not a task credential. See The maintenance model.
Which one do you want?
- "I need to check a resident's rent" → dashboard.
- "I need to pay my rent" → resident portal.
- "How full was my building last month?" → owner portal.
- "Which rooms am I cleaning today?" → dashboard → Cleaning events.
- "I have been asked to fix a boiler" → the link you were sent; there is nothing to sign into.
See Signing in for how each one lets you in.