Click a row to expand it and see ticket options (with early-bird flags where applied), the payment history, and any submitted form responses.
+
+ Set the filters the way you use them, then Saved filters → name them and Save. Click one to apply it; the star makes it the one used when the page opens. They're yours (other people don't see them) and follow you to any device. The Users, Events and Reports pages have them too.
+
Tick registrations (or "Select all shown" after filtering) and choose an action: send a message (email or WhatsApp, as an event update), mark paid (records what each still owes, in cash, EFT, card or other — tickets go out by email), move to another ticket (their tickets and QR codes stay the same; the price follows the new ticket), put their named people in a room or group, export to Excel, or cancel. Each one follows the same rules as doing it one at a time, and you see what happened to each. Moving tickets and groups need registrations from one event.
diff --git a/apps/events/frontend/src/content/help/reports.tsx b/apps/events/frontend/src/content/help/reports.tsx
index 9f4c991..30673d7 100644
--- a/apps/events/frontend/src/content/help/reports.tsx
+++ b/apps/events/frontend/src/content/help/reports.tsx
@@ -29,7 +29,7 @@ export const reportsHelpContent: HelpContent = {
Preview your report, adjust filters, and choose how you want the data to appear.
- Export your report to Excel, PDF, or send it by email or WhatsApp. Tip: select several events in the Feedback summary to compare their ratings (e.g. Camp 2025 vs Camp 2026), or use Series: year on year to compare a whole series' registrations, income and attendance. The Registration funnel shows where people drop off between viewing an event and paying, by source and device. The source comes from short links and utm_source links, else the site the visitor came from (Facebook, Instagram, Google…). The event page's Share and Save QR buttons tag their links as "share" and "qr". WhatsApp doesn't say where a click came from, so add ?utm_source=whatsapp to links you post there, or they show as "direct". It counts only visitors who allowed cookies.
+ Export your report to Excel, PDF, or send it by email or WhatsApp. Saved filters (next to the campus filter) keep a report with its events, dates and options under a name — star one to have it ready when the page opens. Tip: select several events in the Feedback summary to compare their ratings (e.g. Camp 2025 vs Camp 2026), or use Series: year on year to compare a whole series' registrations, income and attendance. The Registration funnel shows where people drop off between viewing an event and paying, by source and device. The source comes from short links and utm_source links, else the site the visitor came from (Facebook, Instagram, Google…). The event page's Share and Save QR buttons tag their links as "share" and "qr". WhatsApp doesn't say where a click came from, so add ?utm_source=whatsapp to links you post there, or they show as "direct". It counts only visitors who allowed cookies.
diff --git a/apps/events/package-lock.json b/apps/events/package-lock.json
index 2e544ed..b8f0fa7 100644
--- a/apps/events/package-lock.json
+++ b/apps/events/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "hope-events",
- "version": "1.49.1",
+ "version": "1.49.2",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "hope-events",
- "version": "1.49.1",
+ "version": "1.49.2",
"license": "ISC",
"devDependencies": {
"@playwright/test": "^1.64.0",
diff --git a/apps/events/package.json b/apps/events/package.json
index 2b41556..afc206b 100644
--- a/apps/events/package.json
+++ b/apps/events/package.json
@@ -1,6 +1,6 @@
{
"name": "hope-events",
- "version": "1.49.1",
+ "version": "1.49.2",
"main": "index.js",
"scripts": {
"dev:backend": "cd backend && npm run dev",