Website, alerts, and programmes
Institution operators configure public chrome and participation without changing product law.
Homepage buttons
Settings → Website → Hero buttons
- Add up to four buttons.
- Choose an allowlisted destination (map, report, learn, docs, section anchors, staff login, and so on).
- Mark exactly one as primary.
- Guests can still browse the map and report UI without signing in; submit still requires verified identity.
Public statistics
Snapshot and impact-band figures default hidden and empty.
Only enable those sections after your institution approves the numbers. Do not publish invented student counts or bin totals.
Alert recipients
Settings → Alerts
- Choose which roles receive in-app and email notices when a report is created.
- Optionally add extra email addresses for mail-only alerts.
- Configure recipients here — do not ask engineering to hard-code office titles into the product.
Ranking boards
| Board | What it measures |
|---|---|
| Ops leaderboard | Closed issues with proof, normalized by unique reporters |
| Community confirms | “I’m seeing this too” on issues that later closed (does not change ops score) |
| Programmes | Staff-attested activities (training, clean-ups, challenges) |
Admin → Programmes is where staff attest programme credits. Programme ranking never rewards raw report spam.
Private report reference
After submit, reporters may see a private reference (for example TC-RPT-…) in confirmation and email.
That reference is for follow-up with the person who reported — not a public anonymous tracking page.