A company admin narrowed to a chosen list no longer sees Company Admin on a teammate's row, because picking it could only ever return a 403. This is the control: a caller who DOES hold every property still sees it.
15 Oct 2026 · branch p7-admin-flip-p6-role-offer · captured against propflow-stage · at 64d30133242
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.
The picker is open on a teammate who is not an admin today, so every entry under it is an offer, not that row's label. This caller holds every property, so the new filter is a no-op for them and the list is intact — Company Admin sits between Maintenance Technician and Property Manager exactly where it did before.
A change that dropped Company Admin from every row would satisfy the unit test that says a narrowed admin cannot see it, and would be a regression for everyone else. The picker is the only place that difference is visible.
What this page is not. The caller is platform staff on the Fairhaven test company — one who holds every property, which is the condition under test, but not a customer company admin. It does not show a narrowed admin's own screen: reaching one needs a login whose building list was chosen on purpose, and minting that is a write this lane may not make. That half is held by the card's unit test and by the route's 403, which this change does not touch.
Asserted in the captured DOM — Company Admin · Maintenance Technician · Property Manager · Leasing Agent · Viewer. Every role this caller may assign is in the open listbox, Company Admin among them — so a reader can see this change removes one option for one kind of caller, not the control.