Paddles Up Docs
Guides

Syncing Registrations to Event Participants

How to reconcile a register listing's registrations with the event's participants list from the Paddles Up app.

This guide is for organization staff running an event linked to a register listing. It lives in the Paddles Up app (https://app.paddlesup.io), not the Register app.

What this is

When an event is linked to a register listing, registrants from register.paddlesup.io don't automatically appear as compete.event_participants in the event. The Sync Registrations queue lets staff reconcile the two sides one row at a time.

Where it lives

  1. Open the event in the Paddles Up app at https://app.paddlesup.io.
  2. Go to the Participants tab.
  3. If the event is linked to a register listing, the Sync Registrations action appears. (If it doesn't, the event has no linked listing.)

What you'll see

A queue with one row per registration. Each row shows:

  • The registrant's name and contact info
  • Their registration status on the listing (Confirmed, Cancelled, etc.)
  • Which option they registered for and when
  • Whether they are currently a compete.event_participants row on the event
  • One-click Add or Remove action

Filters and controls:

  • Search by name/email
  • Filter by registration status or option
  • Drift only toggle to focus on mismatches
  • Manual Refresh

Drift

The view highlights two kinds of drift as a visual warning row but never auto-resolves them:

DriftMeaningSuggested action
Cancelled but in eventRegistration is cancelled but the user is still an event participantRemove the participant if they are no longer playing
Active but not in eventRegistration is confirmed but the user is not an event participantAdd the participant

Drift is intentional — staff sometimes want to keep someone in the event after a refund, or stage participants ahead of opening registration. Sync surfaces the gap so you can decide.

Removing a participant who's on a competition team

If you try to remove a participant who is already on a competition_teams roster, the action is blocked with a CONFLICT toast that names the team(s) to clear first. Edit those team rosters in the competition's bracket / phase view, then retry the remove.

What this does not change

  • No schema changes. Linkage is via (event_id, user_id) against existing tables. Sync just creates or removes compete.event_participants rows.
  • The registration itself is untouched. Cancelling a registration is done from the Register app's staff detail view — see Issuing refunds.
  • Auto-sync is intentionally not provided. Every add/remove is staff-driven.

On this page