MEGAINFRA-WEBAPP/docs/setup
DEls 0857e56cb3 fix(workforce): let site managers add and rename employers and brokers
The employer and broker API routes were never named in the path
classifier, so they fell through to its admin-only default and the
proxy rejected a site manager with a bare {"error":"Not allowed"}
before the route handler ran. The handler's own site scoping was
always correct — it just never got the chance to apply.

- classify /api/employers as dashboard and map it to the workforce
  module, mirroring /api/employees
- let the site dropdown be chosen when adding an employer; only a
  rename freezes the site, which preserves assignment history
- cover the rename path, which had no route test, and the proxy
  gate for the site-manager role
2026-10-19 16:33:41 +02:00
..
api-and-mcp-connections.md
api-route-inventory.md
connection-check-results.json
env-and-mcp.md
local-connection-check-results.json
mega-mcp.codex.toml
mega-mcp.env.example
mega-mcp.hermes.yaml
mega-mcp.json
mega-mcp.remote.codex.toml
mega-mcp.remote.json
production-connection-check-results.json
remote-mcp-check-results.json
remote-purchasing-mcp.md
user-access.md fix(workforce): let site managers add and rename employers and brokers 2026-10-19 16:33:41 +02:00