Building switches under their module rows
Gatekeeper part 3: two per-building switches staff could only flip with a script now show under the Leasing and Renewals rows of the admin customer page. Captured on the Fairhaven Residential (TEST) company on the stage data source.
14 Oct 2026 · branch gk/building-feature-switch-rows · captured against propflow-stage · at fea392401a2+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 · Collapsed: the count of buildings, under Leasing
Under the Leasing module row, Publish the listing when a tenant gives notice says how many of the company's buildings have it on. It is a sub-row of the module, not a second module status. The value comes from each building's own field, read the same way the listing gate reads it.
Asserted in the captured DOM — Publish the listing when a tenant gives notice · Show buildings. The label and the expander are on screen under the module row.
Sections 2–2
2 · Opened: one toggle per building, under Renewals
Under Renewals, Move expired leases to month-to-month opens to one toggle per building, each showing that building's saved value. Nothing is a company-wide toggle, because a company-wide value would have to overwrite some building.
Asserted in the captured DOM — Move expired leases to month-to-month · Hide buildings. The row opened (its button now reads Hide buildings) and the per-building list is on screen.
