The inbox step, state 2 — Clara reads their inbox and writes from a PropFlow address

Lane M, part 1b-2: the state the quiet option puts a company into, and the state a company whose staff chose the PropFlow address is already in — one code path, reached either way.

18 Sept 2026 · branch onboarding/m1b2-propflow-outbound-option · captured against propflow-stage · at e2ae4c3097+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 · State 2 — reading their inbox, replying from a PropFlow address

Flow map ch.4, state 2. The sentence under the title moves the reply half: Clara reads new leads in your inbox and replies from a PropFlow address. Connect your shared leasing inbox so she can read it. The card's From becomes the described PropFlow address, and the line under the buttons reads ✓ Clara writes from a PropFlow address · switch back.

The connect buttons and Skip stay — that is the whole point of the ruling: the inbox is still connected, for the reading half. This org reached the state the second way the ruling allows (staff set the PropFlow address on the customer page); the toggle drives the identical render through the same field.

Asserted in the captured DOMConnect the inbox Clara works from · Clara reads new leads in your inbox and replies from a PropFlow address. · a PropFlow address for your company · Clara writes from a PropFlow address · switch back · Continue with Google · Continue with Microsoft · Skip for now. The moved sentence, the described From (never an invented address), the switch-back line, BOTH buttons still present, and Skip.

State 2 — reading their inbox, replying from a PropFlow address

2 · State 2 at phone width

The same state on a phone: title, moved sentence, card, both buttons, the switch-back line, and the footer.

Asserted in the captured DOMConnect the inbox Clara works from · Clara writes from a PropFlow address · Continue with Google

State 2 at phone width

What the switch-back link does

It POSTs { owner: 'client' } to the same customer-facing route and the screen returns to state 1. The route refuses once Clara is live, with the same sentence the staff customer page answers — so the link is not rendered at all for a live company, rather than offered and then refused.

PropFlow Docs