Team on the settings topic page (slice 8b, part 1)
Team renders through the shared settings topic page: the roster and one building's access list side by side. TEST company only, captured as platform staff.
2 Oct 2026 · branch settings-portfolio/topic-page-s8b · captured against propflow-stage · at 8a7e8a3c889
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 · 1. Team on Company
The same header row as every topic: the tabs on the left, the Invite button and the "i" on the right. With no building picked, the roster stands alone, exactly as before.
Asserted in the captured DOM — Team · + Invite teammate
Sections 2–3
2 · 2. Split: the roster | who can open the building
Property, then the second TEST building: the Company card (the whole roster) stays on the left, and the building's card on the right lists who can open it: company-wide members first, marked "Company-wide: every property", then anyone given that building. Staff and company admins keep the add and remove controls; an admin row never gets one. One building only: no tab offers a second.
Asserted in the captured DOM — + Invite teammate · Company-wide: every property
3 · 3. Phone width
The same split at phone width: the roster first, then the building's list.
Asserted in the captured DOM — Company-wide: every property
