What WorkCore is
What the product does, who each portal is for, and how a repair travels between them.
WorkCore runs building maintenance for a whole organization in one product. A resident describes a problem to an AI assistant, the assistant opens a work order, a superintendent does the work, and a property manager approves anything expensive. Everyone signs in to the same product and sees only the portal for their own role.
At a glance
| Where | Sign in at /login — the site root then forwards you to the home page for your role |
| Who | Residents, superintendents, property managers and leasing staff, inside one organization |
| What you can do | Report a repair and follow it, work the maintenance queue, decide cost approvals, manage units, residents and staff |
| What you cannot do yet | Sign yourself up — access is invite-only — or open a work order by hand from the console: every request starts in a resident's chat |
The four portals
| Portal and where it opens | Who it is for | What happens there |
|---|---|---|
Resident portal, /resident/chat | Anyone who lives in a unit | Describe a problem in chat, follow the repair, rate it afterwards |
Super console, /super/assignments | Superintendents | Work the queue, ask the assistant about contractors, record the completion |
Property manager console, /operator/dashboard | Property managers, admins and organization owners | Approvals, work orders, units, residents, team, settings and the audit log |
Leasing workspace, /operator/leasing | Leasing staff | Prospects, showings and applications |
A resident who has not yet made the AI consent decision lands on /resident/consent instead, and
cannot reach anything else until they answer. See Consent.
Not shipped yet
The leasing workspace opens and its tabs render, but there is no live leasing data behind it yet. The lists stay empty and the + Add prospect and + Schedule showing buttons do nothing.
How a repair travels
- A resident describes the problem in chat. There is no report form anywhere in the resident
portal — the assistant at
/resident/chatis the only way in. Photos can ride along with the message. - The assistant opens a work order. Nothing in the chat thread confirms this, and the
conversation is not linked to the work order it produced. The new request shows up in the
resident's own list at
/resident/work-orders, which refreshes every 60 seconds and whenever the window regains focus. - A superintendent picks it up from their queue. They see the request, its unit, its category, its priority and the photos the resident sent.
- The superintendent arranges the visit. Calling the contractor happens outside WorkCore. The super then tells the assistant who is coming and when, and confirms the dispatch.
- A property manager approves the cost when it is high enough. If the estimated cost is above the property's approval cost threshold, the dispatch waits in the manager's approvals queue until it is approved or rejected. A cost at or below the threshold dispatches outright.
- The work happens, and the super records the outcome with resolution notes, the time spent and up to 5 completion photos. The request then reads Resolved for the resident.
- Closing is a separate, later step. Most requests stop at Resolved. A request moves to Closed when a superintendent asks the assistant to close it; no screen in WorkCore has a button that does it.
Reading a demo build
If a MOCK DATA pill sits in the top bar, you are looking at a demonstration build. The residents, units and work orders on screen are sample records, and messages, comments and repairs you create there never reach a real property team. The pill is absent on a real deployment; there is no matching badge that says the data is live.
Related
- Logging in — the magic link, the invite link, and what the waiting screens mean.
- The resident guide — consent first, then chat, reporting a repair and following it.
- The super guide — one repair end to end, including the steps that happen off the app.
- The property manager guide — approvals, work orders, people and settings.