Onboarding tab — clickable mock

Where a customer answers setup questions before Clara goes live, sees what they answered, and can still look it up afterwards.

2026-09-30 · mock for logic and flow, not final styling · questions from Fede's intake docs and the 9/30 renewals call

Mock switch:

= still needs an answer

Example Property Group › Onboarding

Clara is live. These answers are read-only. To change one, contact your PropFlow team.

How it works

The dot rules

A question has a dot when nobody has answered it, or it only shows PropFlow's suggested answer and the customer hasn't confirmed it.
"Accept recommendation" saves the suggested answer as the company's own answer, which clears the dot.
A section has a dot if any question in it has one. A tab has a dot if any section in it has one. The number next to a section is how many questions are still open.
Company answers cover every building. "This building differs" adds an exception for one building. An exception with no value yet gets its own dot.
Building-only questions (fees) have no company answer. Each building that is blank gets a dot.
"Coming soon" questions have nowhere to save an answer yet. They are shown so the customer knows they are coming, are greyed out, and never count as open.
After go-live everything is locked and a banner says so. Dots stay as hollow rings, so everyone can still see what was never answered.

Decisions taken (2026-09-30)

After go-live the whole tab is read-only. It follows the company's go-live switch. Letting staff reopen editing is a later follow-up, only if someone asks for it.
A PropFlow default the customer never confirmed shows a dot, with "Accept recommendation".
The old password-gated review page stays for now; retiring it is a follow-up.
Collections is hidden until it has questions. Today no document has any.
Questions with nowhere to save their answer show as "Coming soon". Parts 1–5 do not invent storage for them.
Answers save into the real settings the app already reads (fees, office hours, escalation owner, knowledge sections, tour settings, ring lists). There is no separate answers store.
Staff-only until the last part ships.

Where each answer is saved

Every question in the mock shows where its answer is saved, in grey monospace. The short version:

Section	Saves to	Level
Leasing › Hours & contact	`PropertyKnowledge.officeHours`, `tour.*`, company name, signature	company, with building exceptions
Leasing › Fees & deposits	`PropertyKnowledge.pricingDetails.*` + `pricingVerified`	building only
Leasing › Applying / Policies / Tours	knowledge sections (company + `PROP#/KNOWLEDGE`)	company, with building exceptions
Leasing › People	`escalationOwnerEmail`, `ring_list.leasing`, `leasing_digest.recipients`	company, with building exceptions
Maintenance	`maintenance.intake_route`, `catch_all`, `emergency.route.residential`, `vendor_roster.<trade>`	company, with building exceptions
Renewals	`renewal.offerTerms`, `renewal.eligibility` (needs a new save route)	company, with building exceptions
Coming soon	time zone, holidays, what counts as an emergency, Spanish per building, waiting-on-a-part message, renewal follow-ups	—

Setup steps that aren't questions (AppFolio login, mailbox and calendar access, staff list, phone system) belong on the go-live checklist, not in this tab.

How it would be built (5 small parts)

Thinnest working path: an Onboarding tab with Leasing › Hours & contact and one question (office hours) that reads and saves the real field.
Dots, built alongside part 1: an optional "pending" flag on the tab bar and side menu, plus the pending rule with tests.
The rest of Leasing: fees, then the knowledge questions from Fede's core checklist.
Maintenance and Renewals tabs; "Coming soon" questions shown disabled; one new save route for renewal offer terms.
Read-only after go-live, then open it to customers and remove the mock setup guide.

Route: a new top-level workspace tab. If /onboarding clashes with the existing sign-up wizard, it becomes /setup.