Settings → Buildings — the customer turns buildings on or off before go-live
Buildings on/off REVISION 3: a company settings page, not an onboarding step
30 Sept 2026 · branch feat/settings-buildings-page · captured against propflow-stage · at a2871e0e0e+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.
Screenshots and critique rounds
1 · Company › Buildings, light, desktop
The new Company topic page. The page names itself once and says in one sentence what it is for and until when. Under it, how many buildings are on, the customer Buildings table (Building, Units, In Propflow, Notes, Status last as a dot and label; no module columns) and Recent changes with Undo. Buildings sits in the Company group of the left menu, after General.
Asserted in the captured DOM — Choose which buildings Propflow works in. You can change this until you go live. · IN PROPFLOW · STATUS · Recent changes. The page loaded its buildings (not its loading, closed or error state), with the customer columns and Recent changes.
2 · The same page, light, phone
At phone width the page keeps its 16px gutter; the table scrolls inside its own frame rather than widening the page.
Asserted in the captured DOM — Choose which buildings Propflow works in. You can change this until you go live. · IN PROPFLOW · STATUS · Recent changes. The page loaded its buildings (not its loading, closed or error state), with the customer columns and Recent changes.
3 · Turning a building off asks first, with an optional note
Flipping a building's switch off opens the confirm: what turning off does, and an optional note for the Propflow team, which goes on that building's notes thread after the switch saves. Nothing was confirmed in this capture, so nothing was written.
Asserted in the captured DOM — Add a note for the Propflow team (optional) · Turn Off. The confirm opened from the table's switch, with its note field.
4 · Dark, desktop — theme switched through the product's own control
Same page in dark theme. Every colour on the page is a token.
Asserted in the captured DOM — Choose which buildings Propflow works in. You can change this until you go live. · IN PROPFLOW · STATUS · Recent changes. The page loaded its buildings (not its loading, closed or error state), with the customer columns and Recent changes.
5 · Dark, phone
Dark theme at phone width.
Asserted in the captured DOM — Choose which buildings Propflow works in. You can change this until you go live. · IN PROPFLOW · STATUS · Recent changes. The page loaded its buildings (not its loading, closed or error state), with the customer columns and Recent changes.
Two critique rounds, against brand-and-design.md and the approved mock
Round 1. The page renders the customer variant exactly as the mock has it: Building, Units, In Propflow, Notes, Status last as a dot and label (no badges in tables), no module columns; one sentence under the title says what the page is for and until when; Recent changes sits under the table with its own two-sentence empty state. Buildings is listed under Company after General. Found: the count line floated as its own block, 24px from the table, reading as a second subtitle rather than the table's caption. Fixed: the count and the table are one group, 12px apart.
Round 2 (these captures). The count reads as the table's caption. The turn-off confirm opens from the switch with the optional note for the Propflow team. At phone width the page keeps its 16px gutter and does not scroll sideways; the table scrolls inside its own frame. Known and not fixed here, both in the shared BuildingsTable/primitives rather than this page: on a phone the In Propflow switch sits to the right of the table's scroll, so a customer has to swipe to reach it, and in dark theme the on-state Toggle track goes near-white (the same note #14174 carried). No switch was confirmed, so nothing was written to stage; saving, the turn-off note, Undo and the Hidden not-found are pinned by unit tests.