Connect the inbox Clara works from — the company inbox step, no calendar on it
Lane M, part 1: the step is about connecting where Clara reads and writes from. One title, one sentence, the sample card, the buttons, Skip for now. Every calendar state is gone; Google is a plain "coming" line until its consent connects an inbox.
18 Sept 2026 · branch onboarding/m1-inbox-screen · captured against propflow-stage · at e830365fbd+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 inbox step — a company that owns its leasing address
Gera, 2026-09-18, after walking the wizard: make it more obvious that it's about the Gmail experience: connecting where Clara reads and writes from … we don't need the calendar there.
The h1 is Connect the inbox Clara works from
; the one sentence under it says both halves — Clara reads new leads here and replies from this address — and carries Fede's lesson from a customer who connected his personal Gmail by accident. The sample card is one line and signs — Clara
; its caption says what the connection is for.
Below the card: Continue with Microsoft, and where the Google button used to be, a plain line — Google inbox: coming
. Until the Google consent asks for Gmail and stores a mailbox (part 2), that button connected a calendar, which is exactly what Gera hit. The old connect paragraph and the Connect it now
label are gone; nothing sits between the card and the buttons.
Captured as the stage staff company with a client-owned address (the shape whose admin reaches this screen); company_connected=false only selects the company shape of the step, the way the previous evidence pages for this screen were taken.
Asserted in the captured DOM — Connect the inbox Clara works from · Clara reads new leads here and replies from this address · not your personal email · YOUR LEASING EMAIL — SAMPLE · — Clara · Continue with Microsoft · Google inbox: coming — connect with Microsoft, or skip and we'll set it up with you. · Skip for now. The h1, both halves of the sentence, the card's section label (uppercased by CSS, asserted as a person sees it), the sign-off, the Microsoft button, the Google coming line, and Skip. Nothing about a calendar is asserted because nothing about a calendar renders — the frame is the proof of absence.
2 · The same screen at phone width — one viewport
The whole step in one phone viewport: title, sentence, card, the Microsoft button, the Google line, and the footer with Skip for now. Trimming the card to one line and dropping the paragraph over the buttons is what makes it fit.
Asserted in the captured DOM — Connect the inbox Clara works from · YOUR LEASING EMAIL — SAMPLE · Continue with Microsoft · Skip for now
3 · Leasing inbox connected — the heading says what happened
Back from Microsoft with the inbox connected. The same h1 now reads Leasing inbox connected
and the sentence is gone: an instruction over a done state is what Fede reported on 2026-09-11 (it is already saying connect
). A Google inbox consent (part 2) lands on this same view via company_connected=mailbox — there is no third, calendar-shaped outcome any more.
Reached by the redirect's own parameter, so no mailbox row exists behind it on this company — the address slot under the check is empty here, and carries the connected inbox (with its own vendor's mark) for a real connection.
Asserted in the captured DOM — Leasing inbox connected · Clara now answers from this inbox. · Continue. The outcome heading, its line, and Continue. The instruction and its sentence must not be on this frame; the unit test pins that absence, the frame shows it.
What is deliberately not on this screen
No calendar — not a connected-calendar heading, not a calendar status read, not a company_connected=calendar landing. The ruling puts calendars with the people who get an invite; the admin's step is the inbox. The quiet write from a PropFlow address
option and the run-shape change (the step no longer skipped for a PropFlow-owned company, because we still read their inbox) are part 1b, together.