Configure Registration

Work Through The Task

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, Configure Registration narrows that work to safe basics for tiers, add-ons, inclusions, group registration, forms, and publication readiness. Because this is a basics 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 This Task Changes

This is a practical workflow. Read it from top to bottom the first time: the early checks set scope, the middle steps make the change, and the final checks prove the result. The intended readers are Event leads and Registration 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/rego-config?id=:eventId.
• Records or contracts involved: Tiers, Add-ons, Inclusions, and Registration 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.

Follow The Work In Order

1. Confirm the exact scope before opening the tool: Begin by naming the Event Management situation, the owner, and the exact item involved in Configure Registration.
2. Read the visible state before editing anything: Use /rego/events/manage/rego-config?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Make only the change this guide describes: Keep Tiers, Add-ons, Inclusions, and Registration settings in view so the work stays tied to the records or contracts it can affect.
4. Verify the result where another operator would look: 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.

Finish With Proof

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 the event manage page and confirm the event ID matches the event you are configuring. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Open Rego Config and define capacities, registration dates, tiers, add-ons, inclusions, upgrade rules, transfer rules, and group rules. 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 payment configuration and Conditions of Entry before letting attendees register. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Run a test registration path or preview review using realistic attendee choices. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Correct mismatched prices, impossible inclusions, unclear limits, or missing required fields before publication. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. After saving, reload the event and confirm the public registration behavior matches the dashboard setup. This leaves a handoff trail another operator can understand.

What registration config controls

Registration config controls what attendees can choose and what records are created when they sign up.

It can affect:

• Who can register.
• What attendees pay.
• What they receive.
• What questions they answer.
• Whether group registration is allowed.
• Whether upgrades and transfers are possible.

Safe configuration order

1. Action 1. Confirm event capacity and registration dates. Confirm the visible event state before continuing.
2. Action 2. Create tiers. Check the attendee or staff impact before moving on.
3. Action 3. Add inclusions tied to tiers. Keep the event ID and public result in view.
4. Action 4. Add optional add-ons. Confirm the visible event state before continuing.
5. Action 5. Configure group registration if needed. Check the attendee or staff impact before moving on.
6. Action 6. Configure upgrade and transfer rules. Keep the event ID and public result in view.
7. Action 7. Review forms and required questions. Confirm the visible event state before continuing.
8. Action 8. Check payment setup. Check the attendee or staff impact before moving on.
9. Action 9. Test a registration path before publishing. Keep the event ID and public result in view.

Common mistakes

• Add-on price does not match public copy.
• Tier includes an item that inventory cannot cover.
• Required form question is confusing or too private.
• Group rules create accidental over-capacity.
• Transfer or upgrade rules are not explained to staff.

Verification

• Public preview shows correct tiers and add-ons.
• Required fields are clear.
• Capacity and availability are intentional.
• Payment instructions match selected tiers and add-ons.