Settings › Team — give a teammate access to every property

A row action with a confirm step that widens a teammate back to every property through the existing edit route. Captured as platform staff on the stage test company; the confirm was opened, never pressed.

7 Oct 2026 · branch feat/team-widen-every-property · captured against propflow-stage · at 92649c4dd97+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 · Before (main): a property manager's row menu has no way to give every property

On main the row menu only offers removal. The edit route has accepted the every-property word since part 1, but nothing on screen could send it, so a teammate narrowed to a list had no way back through the product.

Asserted in the captured DOM — Remove from team. The menu is open; the screenshot shows it holds no every-property item.

Before (main): a property manager's row menu has no way to give every property
Provenance. Captured from commit 97f06c66f77 plus uncommitted changes, read from the worktree the server was started from (/Users/miniclaw/code/PropFlow/propflowai/.claude-worktrees/team-widen-before) — the server could not report its own commit, so this is the weaker of the two sources. That commit is already merged into origin/main.
Sections 2–3

2 · After: the same row offers "Give access to every property"

The item is offered on the same rules the route enforces for the every-property word: the teammate is within the caller's reach, the caller holds every property themselves, and the teammate does not already read as the whole company. Your own row and a company admin with no list chosen never get it.

Asserted in the captured DOM — Give access to every property · Remove from team. Both items are in the open menu.

After: the same row offers "Give access to every property"

3 · After: a permission change asks first, and says what it means

Choosing the item opens a confirm step that names the person and says plainly what they will see. Only Give access sends the edit; a refusal from the route keeps this open and shows the route's own sentence. The capture stops here, so nothing was written.

Asserted in the captured DOM — Give access to every property? · will be able to open every property the company has now, and any added later. · Give access · Cancel. The dialog's title, its sentence and both buttons are on screen.

After: a permission change asks first, and says what it means
PropFlow Docs