Linked events

A linked event is a separate event kept under this one. It has its own slug, its own public landing page, its own schedule, and its own ticket capacity. It gates nothing on the parent event, and it stays independent apart from being grouped and ordered under it.

When not to use linked events

If what you actually want is a multi-day agenda under one event, one set of tickets, and one registration, linked events are the wrong tool. Use a Multi Day event with sessions instead, and if you need to sell access to specific days separately, restrict a ticket type to specific days on the Tickets tab. That gets you day-by-day agendas and day-scoped tickets without splitting your event into multiple standalone registrations.

Reach for a linked event when the child really is its own event: a pre-conference workshop with separate paid registration, a companion event run by a different team, or a festival's individually-ticketed side stage. If attendees never need to buy a separate ticket or register separately for the child, it isn't a linked event.

Creating a linked event

Open the parent event, go to Linked events under Program, and select Add linked event. Each linked event has the following fields:

• Title: required, e.g. "Day 1: Workshops".
• Day label: an optional short display label (e.g. "Welcome night").
• Day number: controls sort order in the operator list and on the parent's public page. Leave it blank to auto-assign the next position.
• Start / End: this event's own date and time range.
• Venue name: defaults to the parent's venue name if you leave it blank; override for a different location.
• Capacity: this event's own attendee cap, independent of the parent's.
• Status: draft, published, cancelled, or completed. Only published linked events appear on the parent's public page.

A new linked event starts as its own event, seeded with the parent's timezone, venue address, cover image, and currency as starting values. Because it's a full, separate event, you can change any of that later by opening the linked event itself and editing its own settings, tickets, and schedule the same way you would for any other event.

Attaching an existing event

If the child event already exists as a standalone event, use Attach existing instead of creating a new one. Pick the event from the list, and it moves under the parent. It keeps its own tickets, schedule, and registrations, and you can detach it again at any time.

Reordering linked events

Use the Move up and Move down row actions on the Linked events list to change the order. Moving a row rewrites the day number for every linked event under the parent in one operation, so you don't need to renumber the others yourself.

Detaching and deleting

Detaching, from a row's overflow menu, promotes a linked event back to a standalone top-level event. It clears the parent relationship; existing registrations are preserved. Detaching is non-destructive, and you can re-attach the same event later.