Settings company dropdown, part 1: settings name their company (server)
Server-only, held for review. The BEFORE this whole effort replaces: staff with two TEST companies picked top-left get a block instead of settings. TEST companies only.
6 Oct 2026 · branch settings-company-dropdown-p1-server · captured against propflow-stage · at 9f617211809
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 · Before: two companies picked top-left, settings blocks
Platform staff, with two TEST companies picked in the top-left picker (Fairhaven Residential (TEST) and Module Gate Probe (TEST)). Today every settings topic shows this block (#16017). Part 1 changes no screen: it lets the server answer a settings read or write for a company the request names, checked against the caller's own access. Part 2 uses that to open settings on the first picked company with a dropdown in place of this block.
Asserted in the captured DOM — Pick a company in the top-left
What part 1 proves instead of pixels
Cloud test run at the first push: 12 files, 221 passed, 0 failed (company-settings read and write doors, session-org switcher ceiling table, per-company property scope, Team named company, the three route tests, the route-shape censuses). A customer naming a company they do not belong to is refused on read and write by explicit id; staff and the role rules are unchanged.