The complete product blueprint for ApartmentOS — every role, every screen, every journey, mapped before a single line of feature code is written.
Every role sees a purpose-built surface. Underneath, they share the same tokens, the same navigation grammar, the same primitives — so switching context feels effortless.
Public · Buyers · Committees
The front door. Explains the platform and books demos.
Homeowners · Tenants · Family
Daily life inside the community — visitors, bills, bookings.
Committee · Managers
Operate the society. Manage people, money, and property.
Gate staff · Patrol
One-tap gate operations. Optimised for speed under pressure.
Housekeeping · Maintenance
Task list, attendance, and requests — nothing more.
Platform team
Multi-tenant control. Societies, subscriptions, health.
The complete surface area of ApartmentOS across all six experiences. Screens are grouped by role and ordered by frequency of use.
Each flow is mapped end-to-end across actors and systems. Every step is a design surface — and a candidate for automation later.
Every dashboard answers the same three questions in five seconds — what needs my attention, what happened recently, what can I do next — but the answers, and the layout that surfaces them, are unique to each role.
Mobile is not a compressed desktop. Each role gets a tailored bottom bar, oversized touch targets, and gesture-first primary actions.
Resident · thumb-zone approvals
Guard · one-tap gate ops
Staff · task-only surface
A single notification center — categorized, searchable, muteable per category, and delivered through the right channel: push, in-app, email, or SMS based on urgency.
⌘K opens a scoped, role-aware search. Results are grouped by domain and respect the user's permissions — a guard sees visitor logs, a secretary sees the full ledger.
Every module has a defined access level per role. Residents only see their own data; secretaries operate the society; guards operate the gate; staff see their tasks; super admins see nothing personal — only aggregates and audit.
| Module | Resident | Secretary | Guard | Staff | Super Admin |
|---|---|---|---|---|---|
| Visitors | self | full | operate | — | audit |
| Payments | self | full | — | — | audit |
| Complaints | self | assign | — | assigned | audit |
| Notices | read | publish | read | read | audit |
| Amenities | book | manage | — | — | audit |
| Staff | — | manage | — | self | audit |
| Reports | — | full | — | — | aggregate |
| Emergency | receive | trigger | trigger | receive | audit |
| Society Config | — | manage | — | — | override |
Every dashboard in ApartmentOS is measured against the same rubric — regardless of role, device, or module.
The topmost tile is always the single most urgent action.
A quiet ribbon of activity — never louder than what's next.
One primary action per surface. Everything else earns its place.
Next up: Phase 2.5 — interactive prototypes of the three most critical journeys, before we begin building the marketing website.