Event Shepherd

Registration is the switch between "the public can sign up" and "the public cannot". It lives in Settings, in the Configure group of the event sidebar.

The registration switch

Under Registration, one switch controls whether new guests can register for this event.

With it on, your public event page shows the registration form and accepts sign-ups. With it off, the page still exists and still describes the event, but nobody new can register through it.

Turning it off does not affect anyone who has already registered. Their tickets stay valid, they still scan in, their records are untouched.

When to reach for it

Before you are ready. Leave registration off while you build the event, so an early share of the link does not produce a real registration you then have to unpick.
When you sell out. Stock limits close individual tiers automatically. This switch closes the whole event at once.
On the day. Turn it off when you stop taking sign-ups, so the last-minute registration that arrives while the doors are closing does not happen.
When something is wrong. If a price is wrong or a tier is misconfigured, closing registration buys you time to fix it without more people arriving on the bad configuration.

What else closes registration

Three other things stop a registration going through, independent of this switch:

A tier's stock limit. Once a tier's count reaches its stock, that tier stops accepting registrations and reports that it does not have enough remaining stock. Other tiers carry on.

A tier being inactive. An inactive tier is not shown on the public page at all.

The event being closed. Completed and cancelled events freeze their guest records, so no new guests can be added by any route.

Check-in notification emails

The same Settings page carries a second switch, under Check-in notifications, controlling whether guests receive an email when they are checked in.

It is off-by-default territory: helpful for a conference where the email carries the day's programme, unhelpful for a 500-person show where every scan sends a message nobody reads. Decide per event.

Resending tickets in bulk

Also on Settings, Resend Tickets queues a job that sends the ticket email again to every billing contact on the event.

Reach for it when something went wrong for everyone: the event details changed materially, or a batch of emails failed to send. It is a blunt instrument and it will email people who already have their ticket, so for a single guest use Send PDF from that guest's row instead.

Ticket tiers for stock limits and the active switch.
Paid tickets and payments for how a paid registration completes.
What attendees see for the other side of this form.