The Registrations page (under Attendance in the event workspace) is your inbox for everyone who signs up for an event. It shows every registration with its status, payment state, and check-in, and it is where you approve, check in, and manage attendees. Approving and rejecting requires the manage-registrations permission; checking in requires the check-in permission.

The registrations list

The header shows the event name, the number of registrants, and live badges: Occupied (N / capacity, or N confirmed if there is no capacity), plus counts for confirmed, pending, waitlisted, and attended. Built-in view tabs — All, Checked in, Expected, Pending, Waitlisted, Rejected — filter the table instantly. You can also:
  • Search names, emails, companies, job titles, countries, and ticket codes in the Search name, email, company… box.
  • Add filters for Status, Payment, Checked in, and Provider (EventLink or HubSpot registrations). Values within a filter are OR’d; filters are ANDed.
  • Save a filtered state as your own view (Save as view), and rename or delete saved views later. Views persist per event in your browser.
  • Show or hide table columns with the columns menu.

Statuses and payment states

Registration statuses: Pending, Waitlisted, Confirmed, Attended, Rejected, No show. Ticket payment states: Free, Payment due, Paid, Refunded, Canceled. When an event requires approval, new registrations arrive as Pending. When an event is full and its waitlist is on, they arrive as Waitlisted; otherwise they are Confirmed straight away. Approving moves pending and waitlisted rows to Confirmed; rejecting moves them to Rejected. Rejected and pending registrations hold no seat.

Act on a registrant

Click any row to open the detail drawer. It has three tabs:
  • Details — email, status, payment, provider, sales-sequence and Salesforce sync state, company, role, country, ticket code (with a link to the guest’s ticket page), and submission and check-in times.
  • Notes — notes on the linked contact, shared with the Contacts page.
  • Activity — a log of every registration action with time and resulting status.
From the drawer you can Approve, Reject, Check in, undo a check-in with Undo, manually set any status with the status select, copy the email address, or Delete the registration. Delete is only available for registrations that are not Confirmed or Attended and have no ticket. If a Salesforce sync failed, the drawer’s Salesforce row shows the error and a Retry button.

Bulk actions

Select rows with the checkboxes; a toolbar appears with only the actions that apply to the selection:
  • Approve and Reject — for Pending or Waitlisted rows.
  • Check in — for Confirmed rows.
  • Undo — for Attended rows (undoes their check-in).
  • Delete — after a confirmation, removes registrations with no ticket that are not Confirmed or Attended. This cannot be undone.
  • Export CSV — downloads the selected rows (or, with nothing selected, everything currently filtered) as a CSV file.

Check-in at the door

Open Check-in desk from the registrations page (or Attendance → Check-in) for a dedicated scanner and guest lookup desk. See Check-in. If you have the check-in permission, you can use Scan QR on the registrations page at any time. Click it to open the camera scanner: point it at an attendee’s ticket (or invitation) QR code, or type the code and submit. The attendee is checked in and the list updates. You can also check guests in from the row, the drawer, or with the bulk Check in action.

Name tags

Under On-site > Name tags, Eventlink generates one badge per page for every confirmed and checked-in guest. Click Download PDF to print them all, or open a guest’s row to preview their badge and download a single PNG or PDF. Guests without a company have that line left off — the page counts them and links back to Registrations so you can review.

When a guest can’t make it

Guests can cancel their own registration from their ticket page using the ticket code in their confirmation. Self-cancellation moves the registration to Rejected, logs it in the activity log, and is refused when the ticket is already used or void. You see the result immediately in the list; no action is needed from you.

Payments

Tickets show their payment state in the table and drawer. See Stripe for how paid tickets work.