A Workshop is a session type that requires the attendee to register. Each Workshop has its own capacity, deregistration rules, and optional restriction to selected groups. Registration runs only in the attendee app — on the microsite the attendee can see the Workshop, but cannot sign up there. This article describes the registration rules; bundling Workshops into packages (where the attendee picks 1 of 3) is covered in How registration blocks, stages, and tags work.
Decide whether attendees should register for individual Workshops separately, or pick one Workshop from a set (a registration block).
Plan capacities based on the room and the workshop content. The system tracks capacity automatically.
If you want to target communication at people registered for a Workshop, set up Assign to group after registration.
Decide whether attendees can cancel their registration and by when.
Workshop registration rules are configured at two levels:
At the session-type level — defaults for all sessions of that type. Set once, and every Workshop of that type inherits them.
At the individual session level — an override of the default for one specific session.
Both levels expose the same set of registration fields.
Assign attendee to a group after registration. After a Workshop registration, the system automatically adds the attendee to a chosen group. The group must exist in advance under Contacts and groups.
Use case: targeting communication only at attendees of a specific Workshop (a personalized e-mail, a push notification, special content in the app visible only to that group).
Registration only for selected groups. Workshop registration is restricted to attendees in specified groups. Other attendees can see the Workshop (unless visibility is also restricted), but cannot sign up.
Use case: VIP Workshops for paying attendees, closed Workshops for a specific corporate team.
Limit total registrations. The maximum number of attendees in the Workshop. Once full, the Workshop is marked Fully booked in the app and further registrations are blocked.
Show the number of available spots. If capacity is limited, you can show the remaining count to attendees in the app. Transparent for the attendee, but it can create pressure ("hurry, only a few spots left").
Session deregistration. The attendee can cancel a registration (and free up the spot for someone else). Two options:
Relative to session start — a relative time before the session starts (1, 2, 6, 12 hours, 1, 2, 7 days, and so on).
Specific date — a fixed date and time. After this deadline, no one can deregister.
Notify the organizer when an attendee changes registration. An e-mail to the organizer on every registration or deregistration. Useful for Workshops with an assistant who plans capacity (catering, materials).
Notify the attendee when registration changes. An e-mail to the attendee on registration or deregistration. The standard confirmation.
Send ICS to attendee. After registration, the system e-mails the attendee an ICS file so they can add the session to their calendar.
The attendee opens the attendee app (mobile or web) and finds the session in the Agenda.
On the session detail they see the Register button (if it is not full and they meet the visibility conditions).
After tapping it, the system registers them automatically. If configured, they get a confirmation e-mail with the ICS.
The session shows up in My Agenda.
If deregistration is allowed, the session detail shows a Deregister button (until the configured deadline).
Registration through the microsite is not available — the attendee must sign in to the app. The reason: Happenee keeps registrations tied to an attendee identity.
Happenee does not currently support a waitlist. Once capacity is full, the Workshop is marked as full and further registrations are rejected. If someone deregisters, the spot opens up and another attendee can register (but not automatically from a waitlist — they have to actively click Register).
On the Visibility tab of the session panel:
Public — every attendee sees the Workshop.
Selected groups only — only attendees in the chosen groups see the Workshop. Everyone else does not see it in the Agenda at all.
The difference compared to Registration only for selected groups: a visibility restriction means the attendee does not see the Workshop at all; a registration restriction means they see it but cannot sign up.
Without a block: the attendee can register for any number of Workshops. Useful for optional Workshops or training programs with several parallel streams, where the attendee builds their own itinerary.
With a block: the attendee picks 1–N Workshops from a set. Useful for a format like "in the morning you pick one of three Workshops, in the afternoon another one of three". Detail in How registration blocks, stages, and tags work.
Always set the capacity — the system blocks registrations once the limit is reached. Without the setting, capacity is unlimited.
Workshop registration is only in the attendee app. On the microsite the attendee sees the Workshop, but for registration they have to go to the app.
Create the group first in Contacts and groups, then assign it to the Workshop.
Set a sensible deregistration deadline — for example, 24 hours before the session starts or 72 hours before the event starts (for catering).
Capacity can be increased at any time. Lowering it below the current registration count is not allowed — the system blocks it. To lower the capacity, you first have to deregister attendees manually.
Check that the attendee has visibility of the Workshop (groups) and that the session status is Published. A third option: the attendee is not registered for the event (they have to be signed in to the app with the Attending status).
