Team gets the Company | Property scope

Settings > Team: the Company tab is the roster as before; the Property tab lists who can open one building. TEST company only.

1 Oct 2026 · branch settings-portfolio/team-scope · captured against propflow-stage · at 1a7cb515001+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 tab

No query string: the Company tab. The roster, the invite button and every row control are unchanged; the scope tabs sit above the card.

Asserted in the captured DOM — Company · Property

Team page, Company tab, with the scope tabs above the roster

2 · The Property tab, one building picked

Picking a TEST building lists the people who can open it: company-wide members marked "Company-wide: every property", then anyone scoped to that building. A scoped row's menu offers "Remove from this property"; the picker under the list gives a teammate access. Both are the existing building-list edit, on the route's own rule.

Asserted in the captured DOM — Company-wide: every property

Team page, Property tab, listing who can open the picked building

3 · Phone width (390px), the Property tab

390px: the tabs and the list fit the screen with no sideways scroll.

Asserted in the captured DOM — Company-wide: every property

Phone width Property tab
PropFlow Docs