Workshops and breakout rooms

A workshop is an event inside your event. It has its own room, its own start and end, its own seats and its own tickets — priced independently of the main ticket, free or paid.

Studio → your event → Workshops.

Adding one

Name, room, start, end, and how many seats the room holds. It lands as a draft, like any event, so price it under its own Tickets screen and then publish it.

The workshop list shows No tickets against anything that cannot be published yet, which is the one thing worth catching before the day.

What guests see

Workshops appear on the parent event's page under Workshops and breakout rooms, with the time, the room, the price and how many seats are left. Each one is booked separately.

Workshops never appear in browse. Twelve breakout rooms would bury every other event on the day they run, and they belong on their parent's page.

Why each one issues its own ticket

Because your door staff scan people into rooms.

A ticket can be scanned once per day. If one ticket had to serve both the main entrance and Room 2, the second scan would be read as the same person arriving twice and quietly ignored — no record that anyone attended the workshop.

Separate tickets mean separate scans, so you get real attendance per room. It also means nobody has to enforce who is allowed in: somebody who did not sign up simply has no code for that room.

Clashes

An ordinary attempt to book two overlapping workshops is refused, naming the one the guest is already in. A double booking takes a seat out of a small room that nobody can use.

The migration target still has a concurrency gap: two simultaneous bookings into sibling workshops can pass the overlap check. Do not use that check as the only scheduling control until the known issue is closed.

Nesting

One level. A workshop cannot have workshops of its own, and an event that already has workshops cannot be put inside another. This is enforced in the database, because the visitor counts on the trade fair report depend on it.