Roadmap: 1.44.0 campus-scoped staff decisions

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-27 17:17:32 +02:00
co-authored by Claude Opus 5.5
parent eff2cb108b
commit ab4152960b
+23
View File
@@ -581,6 +581,28 @@ install. It ships in **two releases** (2026-10-27):
the read-only route test), so new endpoints can't skip the check.
- The heartbeat's `features.campuses` / `stats.campuses` report the real setting
(hard-coded `false` until 1.43.0).
- **How each kind of endpoint is checked:** event id in the URL → a route middleware
(`scopeEvent`); a record that belongs to an event (registration, ticket/QR, waitlist
entry, option, bundle, allocation set…) → traced back to its event, same check;
lists across events → the controller adds the scope `where` (route marked so the
test knows); an event named in the body → checked before saving; nothing to do with
an event → allowed or unscoped-only, listed with a reason.
- **Rules (decided 2026-10-27):**
- Admins are never scoped. Scoped supervisors and staff see their campuses' events
plus "All campuses" events.
- "All campuses" events: scoped staff can view, scan, take payments at the door and
do manual registrations; event setup, options, bundles, cashup and refunds stay with
admins and unscoped supervisors.
- Site banner, payment-provider reconciliation and donations not linked to an event:
admins and unscoped supervisors only. Ad-hoc broadcasts: scoped supervisors only to
their campuses' audiences and their events' attendees. Coupons: only for their
campuses' events.
- Another campus's records answer "not found" (nothing leaks); the scanner instead
says which campus the ticket is for.
- While campuses are off, scopes are ignored (everyone sees everything); the Campuses
tab warns which staff are limited before turning campuses off.
- Scopes are set by admins in Admin → Users ("Limit to campuses"); changes are audited
(`user_campus_scope_changed`).
### Data model (sketch)
@@ -961,6 +983,7 @@ feature.
| — | POPIA: re-accepting the notice | The admin decides per version ("significant change — ask everyone to accept again"); people are asked once after login (2026-10-23) |
| — | POPIA: inactive accounts | Anonymised after 5 years without a login or registration, **on by default**, with a warning email 30 days before; staff/supervisor/admin accounts never (2026-10-23) |
| — | Product name | **Cross Events** (was Hope Events), Hub: **Cross Events Hub**. UI text and docs renamed in 1.41.3; technical identifiers (`hope-events` repo, storage keys, encryption salt, migrations, PM2/nginx names) stay, so installs and sign-ins keep working (2026-10-27) |
| — | Campus-scoped staff (1.44.0) | Scoped staff: their campuses' events plus "All campuses" events, which they can view, scan, take door payments and do manual registrations for, but not set up, cash up or refund. Banner, provider reconciliation and unlinked donations: unscoped only; broadcasts limited to their campuses' audiences and their events' attendees; coupons only for their events. Other campuses' records answer "not found" except the scanner, which names the campus. Scopes ignored while campuses are off, with a warning (2026-10-27) |
| — | Multi-campus split | Two releases: **1.43.0 campuses**, **1.44.0 campus-scoped staff**; everything after moves up by one. Scoped staff can view and scan "All campuses" events, only admins and unscoped supervisors edit them. "Everyone at campus X" = home campus X, plus (tick box) registrants of campus X's events in the last 12 months. Campus landing pages are in 1.43.0 (2026-10-27) |
| — | Updates | Sites show **Request update**, never the deploy command: the request goes to the Hub, which tells Joshua; he updates the server. 1.42.0 / Hub 1.1.0; Multi-campus and everything after moves up by one (2026-10-27) |
| — | POPIA: WhatsApp STOP | In 1.38.0, via WAWP's incoming `message` webhook with a secret in the URL (WAWP doesn't sign webhooks) (2026-10-23) |