Connecting AppFolio also seats the company
PR #10550 — the wizard's AppFolio step now asks which AppFolio user account we send from, and posts it in the same request as the key. Captured from the branch's own dev server.
21 Sept 2026 · branch feat/onboarding-writes-org-clara-seat · captured against propflow-stage · at 494629066a+local
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 · The seat question, revealed once the credentials are done
The three credential fields still reveal one at a time; the seat question is the fourth thing this screen asks, after the last of them is committed, and it sits inside the form above Where do I find these in AppFolio?
rather than below it. The first cut of this change rendered it unconditionally after the form — two seat boxes on screen before Client ID and Client Secret had appeared, under the help link, with the reserved space for the unrevealed fields as a hole between them. The capture is what caught that; no test could have.
One section, two fields, one sentence saying why it is asked. Composed from the same floating-label input the credential fields use. Nothing names a field or a system: an admin reads AppFolio user ID
.
Asserted in the captured DOM — Who we send as in AppFolio · AppFolio user ID · Name shown on its messages. The section heading and both labels, in the rendered DOM. If the fields were not mounted the capture would fail rather than produce a reassuring picture.
2 · Connect pressed with a NAME typed where the ID goes
Attribution compares ids, so a name in the ID box would never match and every one of our own sends would be re-imported as if a teammate had written it — a failure with no symptom at the point of entry. The message lands under that field, in red, and says what to do rather than what is wrong. Nothing is sent: the round trip is spared and no partial connect can happen.
Asserted in the captured DOM — Numbers only. The sentence is in the DOM only after the press — the same reveal-on-submit contract the credential fields follow.
3 · The same step on a phone
At phone width the new section stacks with the rest of the form and stays inside the same gutter — it inherits the screen's layout rather than bringing its own.
Asserted in the captured DOM — Who we send as in AppFolio
