Waitlist for one activity within a complex event

In GiveCampus Events, available controls depend on your permissions and the interface used by your institution.

The native waitlist belongs to the overall event registration, not an individual activity. An activity can have a ticket/guest limit, but reaching that limit does not create an activity-specific waitlist queue. If only one session needs a queue, keep its capacity accurate and use an institution-managed external waitlist, reviewing availability before inviting someone to edit their registration. If an independent native waitlist is essential, consider a separate event for that session. This changes the registration structure; do not assume that enabling the parent event waitlist supplies a queue for each activity.