pf_app/routes
Paul Trowbridge 39b2a7e4a2 Only the author or an admin can edit a log entry
PATCH /log/:logid had no check, so any account could edit the tag, note,
label and bucket of any entry -- including loads whose rows it cannot see.
That reads as harmless annotation and is not: label and bucket name the
pivot's columns for everyone in the version, so a rep could rename the
company's segments.

Same rule as undo now, author or admin, with the fields shown read-only
rather than editable-then-403 -- in the change log's tag and note cells and
on the Baseline page's label and bucket.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-18 12:06:13 -04:00
..
auth.js Read territory at login, and survive having none 2026-09-18 11:52:00 -04:00
log.js Only the author or an admin can edit a log entry 2026-09-18 12:06:13 -04:00
operations.js Scope what an account can see and change to its territory 2026-09-18 11:14:03 -04:00
sources.js Put the territory column in the Setup editor 2026-09-18 11:38:55 -04:00
tables.js Expose pf_note/pf_op in forecast data; fix tables list duplicates 2026-04-28 19:51:45 -04:00
versions.js Put the fallback display names on the version 2026-09-17 23:47:17 -04:00