Every leasing company walks the inbox step — the PropFlow-owned state
Lane M, part 1b-1: the address owner no longer removes the Channels step or its connect buttons. A company whose replies go out from a PropFlow address still connects its inbox so Clara can read it.
18 Sept 2026 · branch onboarding/m1b-run-shape-google-button · captured against propflow-stage · at cfc68b366a+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 · PropFlow-owned address — the step, with its connect buttons
Until this PR a company whose address PropFlow owns had this screen removed from its run (#9321, the 2026-09-17 skip) and, if it reached the URL, saw the card with no buttons and a footer Continue. Gera's 2026-09-18 ruling put it back: we still read it, but we write through PropFlow
. The card describes the PropFlow address the reply comes from; under it, the Microsoft button, the Google line and Skip for now — the same controls a client-owned company gets, because the inbox is connected for the reading half either way.
The stage staff company's address owner was set to propflow for this capture (a stage write on a non-customer org) and set back after.
Asserted in the captured DOM — Connect the inbox Clara works from · a PropFlow address for your company · Continue with Microsoft · Google inbox: coming · Skip for now. The title, the card's described From (a PropFlow address, never an invented one), the Microsoft button, the Google line and Skip — the controls that were absent for this owner before. No footer Continue is asserted because none renders; the frame shows its absence.
2 · The same state at phone width
One viewport: title, sentence, card, the Microsoft button, the Google line and the footer with Skip for now.
Asserted in the captured DOM — Connect the inbox Clara works from · Continue with Microsoft · Skip for now
Not captured, and why
The unset owner (a company staff never set up) renders the identical controls under a card that says a PropFlow address for your company · We'll confirm this address with you
; the unit test pins it. No route unsets emailSetup on a row that has it, so that state is not photographable on stage without a direct table write, which this lane does not make. The Settings card's connect form for these owners is pinned by EmailSetupCard.shapes.test.tsx; the settings page needs a customer admin whose company is on that owner, which the evidence identity's company is not.