Leasing & tours — the property's switches are grid rows
The property's five Leasing switches are rows of the scoped grid, in every column. TEST company only.
1 Oct 2026 · branch settings-portfolio/pr1g-part2 · captured against propflow-stage · at adbf97a1a0e+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 · A property column
One TEST building picked. Five switch rows; the old card below the grid is gone.
Asserted in the captured DOM — Tour length · Application link · Guest card after a call · Guest card note after a text · Email when a tour can't be booked · Email when a booked time is gone · Text the prospect when a booked time is gone
2 · A property and two compare columns
Two compare columns: a switch per building in every row. No TEST building has Leasing off, so that column is covered by tests only.
Asserted in the captured DOM — Guest card after a call · Text the prospect when a booked time is gone
3 · The Company column
Company scope: each switch row reads "Set per property".
Asserted in the captured DOM — Company · Tour length · Set per property · Guest card after a call
4 · Phone width (390px), a property column
390px: rows stack, each switch under its label.
Asserted in the captured DOM — Guest card after a call · Email when a booked time is gone
