Conditions, Payments, and Notifications

Use This Dashboard Area Safely

Use this guide when event setup, attendee operations, staff work, payment-adjacent tasks, public pages, or closeout records need a controlled path. In this guide, Conditions, Payments, and Notifications narrows that work to conditions of Entry, payment setup, payment providers, notification config, and Google Wallet. Because this is a surfaces page, read it as part of the Event Management learning path rather than as an isolated checklist.

Event records become real-world instructions: what attendees see, what staff do, what money or inventory must reconcile, and what future organizers inherit. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Event leads, Finance staff, and Communications staff. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/conditions-of-entry?id=:eventId, /rego/events/manage/payments-config?id=:eventId, /rego/events/manage/notification-config?id=:eventId, and /rego/events/manage/google-wallet-config?id=:eventId.
• Records or contracts involved: Conditions of Entry, Payment providers, Notification settings, and Wallet settings.
• Main care point: Watch for changing one part of the event without checking attendees, staff, finance, communications, public information, and closeout records.
• Proof worth keeping: event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the Event Management situation, the owner, and the exact item involved in Conditions, Payments, and Notifications.
2. Read the current state before changing it: Use /rego/events/manage/conditions-of-entry?id=:eventId, /rego/events/manage/payments-config?id=:eventId, /rego/events/manage/notification-config?id=:eventId, and /rego/events/manage/google-wallet-config?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Conditions of Entry, Payment providers, Notification settings, and Wallet settings in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff so the next operator can see what changed and why it was safe to continue.

Before You Leave The Screen

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on attendees, staff, money, public pages, communications, and post-event records.
3. Proof is findable: The handoff points to evidence that the next operator can see what changed and why it was safe to continue.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Anchor the work to one event. Open Conditions of Entry, payment configuration, notification configuration, or Google Wallet configuration for the correct event. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Update one responsibility area at a time: policy text, payment account/instructions, notification copy, or wallet settings. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Change only the intended event setting or record. Check that payment wording, policy requirements, and attendee-facing messages do not contradict each other. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Preview or reread rendered markdown-ext content before saving. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Save, reload, and confirm attendee-facing pages or emails show the expected content. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. If payment or policy information is uncertain, keep registration unpublished until the owner confirms it. This leaves a handoff trail another operator can understand.

Conditions of Entry

Conditions of Entry are policies attendees must accept. They should be readable, assigned correctly, and updated before registration opens.

Payments config

Payments config controls providers, accounts, instructions, and payment report behavior. Finance staff must verify this before attendees pay.

Notifications and Google Wallet

Notification config controls event communication behavior. Google Wallet config controls pass-style attendee artifacts where enabled.

Common mistakes

• Conditions are written after attendees already registered.
• Payment account is inactive or wrong.
• Instructions do not match actual finance process.
• Notification audience or copy is unreviewed.
• Wallet pass settings are enabled without testing.

Verification

• Conditions save, order, assign, and render correctly.
• Payment provider/account settings reload correctly.
• Notification settings are intentional.
• Wallet config is tested before promotion.