Owners, managers & users

Manage existing events and registrations

Review schedules and capacity, process attendance requests, and explain the public registration page to attendees.

Browse all guides

This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.

Start here

  1. Open Existing Events and identify the event by Title, Schedule and Created by.
  2. Check Attendance for reserved places versus capacity, and expand Registrations to inspect submitted requests.
  3. For an event you manage, select Pending, Confirmed or Declined beside the intended registration and choose Update.
  4. Use Public page to check and share the event. Direct attendees to Register your interest when registration is required.
  5. Use Edit for details, Cancel to mark the event cancelled, Republish to restore it, or Delete only when the event and registrations should be permanently removed.

Read the event list

Each row shows Event, Schedule, Created by, Attendance, Registrations, Status and Actions. Open events display Open event and Not required for registration. Registration events show reserved spots over capacity and a separate submission count. One submission can request more than one spot.

The owner sees network events. Managers see events within their permitted hierarchy; edit, registration-review, cancellation and deletion controls are available only for their own events. If no events appear, choose Create Event or check your account scope.

Review and update registration requests

Expand the submission count to see each request’s name, status, requested spots, TikTok username, telephone, email, optional Discord / Snapchat and notes. Identify the right person before using the status selector and Update.

Pending and Confirmed requests reserve capacity. Declined requests do not. Changing a declined request back to pending or confirmed checks that enough places remain. Confirming is a status update in the site; this page does not promise to email an attendee automatically. Use the displayed contact information for any separate communication needed.

Help attendees use the public event page

Public page opens the event without a dashboard login. It shows the schedule, location, About this event, gallery when present, and cancellation state. Gallery images can be opened separately. For a registration event, the public page displays remaining availability or explains that it is full, ended, closed or already submitted.

The attendee enters Full Name, TikTok Username, How many spots do you want to reserve?, Tel and Email. Spots must include the attendee and any guests. Discord / Snapchat and Notes are optional. Submit interest sends the details and spot count to the event manager and network owner. The success page says the requested spots can now be reviewed; it is not an automatic confirmed-attendance message.

The page blocks repeat submissions from a device it recognises and duplicate registrations for the same email. An attendee who needs to correct a request should contact the organiser instead of repeatedly submitting. The available capacity is checked again when the request is saved, so a place can disappear while someone is filling the form.

Cancel, republish or delete

Cancel marks the event cancelled. The public page then displays a cancellation notice and closes registration. Republish changes it back to published; the event’s other time and capacity checks still apply. These actions retain the record.

Delete confirms removal of the event, all images and all registrations. It permanently removes the event and its public availability rather than simply marking it cancelled. Use Edit to correct information, and Cancel when you need a visible cancellation record.

Resolve common capacity problems

When the number of reserved spots is higher than expected, expand registrations and total the spots requested, including pending submissions. Declining a request frees its places. The form count alone does not measure occupancy.

A failed registration restoration means the other active requests plus the restored request would exceed capacity. Increase capacity in Edit if appropriate, or keep the request declined. Do not treat a failed update as a successful booking.

Frequently asked questions

Why are pending requests counted as reserved?

The event capacity calculation includes every request except Declined. Pending requests therefore hold their requested spots while you review them.

Can I restore a declined request after the event fills?

Only if there is enough capacity for its full spot count. Otherwise the update is refused.

Does Submit interest confirm attendance?

It submits a request for the manager to review. The success message says spots were requested. The manager controls the status.

What is the difference between Cancel and Delete?

Cancel preserves the event and shows it as cancelled publicly. Delete removes the event, images and registrations permanently.

Why can an attendee not submit twice?

The public form checks repeat submissions on the device and duplicate email registration. Ask the organiser to review the existing request.

Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.