Onboarding tab, part 5b: a customer before go-live
A property manager at a pre-live company sees Onboarding in the rail and can answer; the on-call list stays PropFlow's
1 Oct 2026 · branch feat/onboarding-open-to-customers-p5b · captured against propflow-stage · at cb010ef64b8
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · A pre-live customer answers Hours & contact
Signed in as a property manager at a company that is not live yet. The rail shows Onboarding, with no Admin or staff rows. The questions are editable and open answers carry dots.
What to look at
Each Save goes through the route that already owns the answer. Every route accepts this login only while the company is not live, and the same login is refused (403) once it is. The Coming soon rows are staff-only, so a customer does not see them.
Asserted in the captured DOM — Onboarding · Hours & contact · Office hours · Save. The tab rendered for a customer, editable.
2 · Leasing › People, pre-live
Who gets escalations, the leasing ring order and the lead-summary list are all editable for this customer before go-live. The lead-summary list now loads through the company-scoped door from 5a-ii.
Asserted in the captured DOM — Who gets escalations · Leasing call ring order · Who gets the lead-summary email · Saving at least one address
3 · Maintenance › Emergencies: the on-call list stays PropFlow's
The on-call rotation shows read-only, with no Save, even before go-live. PropFlow sets it (decision b90280944).
Asserted in the captured DOM — On-call rotation
Two critique rounds
Round 1 and round 2
Round 1 (first capture, before 5a-ii landed). The lead-summary question read We couldn't load this answer for the customer. It still called the staff-only admin route. That was the gap 5a-ii closed, and the recapture shows it loading. Round 2 (against brand-and-design.md). The rail carries only customer rows (no Admin, no staff sections). The on-call list renders read-only with no Save and no live banner, so nothing offers an edit the server would refuse. The dots and cards use the same shared components as the staff view, with no new colour drawn by hand. Nothing was saved in any capture.