Onboarding inside Settings: evidence
Built from the approved mock. Screenshots come from each branch's own dev server on the anonymized stage table, signed in as the staff smoke user. Pre-live companies are stage TEST companies. The live company is an anonymized stage copy.
The customer's onboarding now lives at Settings › Onboarding (/settings/onboarding). Opening a module stays inside Settings, and the old /onboarding-guide/… and /settings/go-live links redirect there. Each part below is one small PR, with its screenshots folded inside.
Part 1: Stay in Settings #15340 merged (9064fdeb)
The Settings menu has an Onboarding group: Overview, Leasing, Maintenance, Renewals. The module page has no header, tab bar or back link of its own. Its sections are a list on the left, and the module row stays highlighted in the Settings menu. It works at phone width (the Settings picker reads “Onboarding: Leasing”) and in dark mode. After go-live, the same page is read-only with a banner. The menu moves the group to the bottom for a live customer. Staff always see it at the top, because the server cannot tell which company they picked.
Part 2: The friendly hub #15532 open
The Overview opens on a progress ring (questions answered, and setup steps done out of 3) and the four steps to go-live, with the first unfinished step highlighted. Below that is one card per module with a plain blurb, "N left", a bar and Continue, and then the setup rows. No numbers are invented: a failed read shows "—" and Unknown, never progress. After go-live it reads "You're live" and the cards say Read-only. The partly-done and done states are drawn from a stubbed status, because stage has no TEST company in those states. The empty and live states use real stage data.
Part 3: The Leasing page frame #15533 open
Each module page explains itself before it asks: a title, "What Clara does here", and a five-step flow where each step names the question steps that control it. The sections become numbered steps with answered/asked counts and dots, with "N of 25 answered" in view and Back/Next at the bottom. After go-live it is the same frame with no counts.
Part 4: Choice cards opens after part 1
Closed-set questions become big cards: tour length, travel time, the application link, office-hours presets, the escalation person (teammates) and the ring order (tap in order). A tap saves at once through the same write Save makes. Typed answers sit behind "Other" and keep their Save. "Recommended" appears only on tour length 30, and travel time "back to back" reads "Our default". Those are the only values acceptRecommendationPlan recommends. Office hours get presets, never a badge.
Part 6: Maintenance and Renewals opens after part 4
Maintenance and Renewals get the same intro and flow. The renewal rent is three cards, never badged, because the rent is the customer's money. If nothing is stored, no card is pre-checked. The renewal limits keep the "Until you answer, Propflow uses…" line, and there is no "keep current limits" card until Gera decides.
