Connections — one page, its scope picked by the bar
Connections gets the [Company | Property] bar: the company's property system, or one building's calendar and mailbox. The old building URL lands on the property scope. TEST company only.
1 Oct 2026 · branch settings-portfolio/connections-scope · captured against propflow-stage · at be8baba7473+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 Company scope
Company scope: the bar over the company card, the property system, exactly as before.
Asserted in the captured DOM — Connections · Company · AppFolio
Sections 2–4
2 · A property's scope
One TEST building picked in the bar: that building's card, the one the old building page showed. The TEST company connects its mailbox once for every building, so the row says so; the building's own calendar picker shows for a company that has not.
Asserted in the captured DOM — Microsoft 365 · Connected for your company · Clara reads rents and what's open from here
3 · The old building URL
/settings/property/connections redirects to the property scope. With the whole company picked in the top bar there is no one building, so it asks for one.
Asserted in the captured DOM — Connections · Pick a property
4 · Phone width (390px), a property's scope
390px: the bar wraps and the card fits, with no sideways scroll.
Asserted in the captured DOM — Microsoft 365 · Clara reads rents and what's open from here
