A co-managing company's admin sees the shared building, and none of the owner's others

Board row p7-relationships (block b90533331): the stage capture Gera accepted as proof beside the automated tests. One building of a TEST owner company is co-managed by a second TEST company; that company's admin login sees it on a soft switch and a hard load, and sees none of the owner's other 69 buildings.

8 Oct 2026 · branch detached · captured against propflow-stage · at 06bea3ebfc5

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 · Hard load: the co-manager's admin on Properties

A fresh document load of /properties, signed in as the co-managing company's admin (MS Proof Co, an org_admin with no staff access). The grid holds the company's own MS Proof Building and the shared building 2839 1/2 Micah Court, whose record belongs to the owner company Wei Slope Mirror (TEST).

Asserted in the captured DOM — MS Proof Co · 2839 1/2 Micah Court · MS Proof Building. The shared building and the company's own building, in the rendered grid after a document load. The full page is asserted (fullPage), so nothing below the fold is hidden from the check.

1 · Hard load: the co-manager's admin on Properties
/properties, hard load, as the co-manager's admin.
Sections 2–2 and notes

2 · 2 · Soft switch: side rail from the Dashboard to Properties, no document load

A separate tab loads /dashboard and then follows the side rail's Properties link, a client-side navigation with no document load in between. The shared building is there after the in-app move, as it is on the hard load.

This login holds one company, so there is no company switcher to drive: the soft half of the bar here is the in-app navigation.

Asserted in the captured DOM — MS Proof Co · 2839 1/2 Micah Court · MS Proof Building. The same three strings after the side-rail navigation.

2 · Soft switch: side rail from the Dashboard to Properties, no document load
/dashboard → side rail → /properties, no document load.

The negative, the expected non-admin result, and how this was run

Negative, as the admin: none of the owner company's other buildings. With the same share live, an independent read-only check loaded /properties, /tenants and /dashboard as this admin and searched the rendered text for every one of the owner company's 69 other building names, read from its roster on stage. 0 of 69 appeared on any page. The shared building did appear on /properties and, through its residents, on /tenants.

No "shared" marker. The grid does not mark the co-managed building as shared. It shows the building's own ticker (161) like any other card. The scope label above the grid also still reads All Properties 1 while the grid shows two buildings. Both are recorded here as observations, not findings.

Expected result for a non-admin manager (recorded, not a bug). The same share was captured earlier today for a property_manager of the co-managing company who holds every building of that company (holdsEveryBuilding: true). That login did not see the shared building: /properties showed only the company's own building, and naming the shared building directly was refused (org_not_answerable). It also saw 0 of the owner's 69 other buildings. Per rulings f6f0a1a18 and f08ab53c7 (citing f97e6f9b4), this is the correct current behaviour. A co-managing company's admins see the shared building. Non-admin manager staff reach it only through a per-building actingForParty grant, which is part 2b of that work and is not built yet. Whoever builds part 2b should rerun this exact capture with the every-building property-manager evidence identity; that half is expected to flip.

How this was run.

PropFlow Docs