JEM 5.1.0
Tickets
Use Tickets to follow reservations, available places, payments and admissions across your events. Start with the overview below, then choose a guide for the operation you need.
Payments and admission
Find a reservation, record a cash or verified bank payment, and admit people using their QR or locator.
Read the guide →
Change reservation area
Move confirmed places between areas, review price differences, record the reason and notify the holder.
Read the guide →
Practical examples
Follow worked examples for free admission, payment at the desk, and moving places together.
Read the guide →
Open Tickets
In the Joomla administrator, open Components → JEM and select Tickets in the Data section. The events and actions you can see depend on your permissions.
A Tickets menu item can also provide authorised staff with access from the frontend. The frontend page does not grant additional permissions: payment, admission and reservation-management rights still apply separately.
Understand the three parts of a booking
| Part | Question it answers | Example |
|---|
| Reservation |
Does this person have confirmed places? |
A reservation for two places is confirmed. |
|---|
| Payment |
Has the required amount been received? |
The reservation is confirmed, but €20 is still due. |
|---|
| Admission |
How many of those places have been used to enter? |
One person has entered; one place remains unused. |
|---|
A confirmed reservation is not necessarily paid. A paid reservation is not necessarily used. A free confirmed reservation can be admitted without recording a payment.
Read the table
The figures count places, not orders or unique people. A single reservation for four people contributes four places.
| Column | Meaning |
|---|
| Date / Time |
The event date and start time, displayed compactly. |
|---|
| Programme / Event / Area |
The event structure, including programme children and configured spaces or capacity areas. |
|---|
| Capacity |
The configured bookable capacity, subject to the event and area limits. |
|---|
| Reserved |
Places held by the organiser, separate from confirmed registrations. Where available, the tooltip breaks down the organiser's total, available, assigned and confirmed places. |
|---|
| Confirmed |
Currently confirmed places, including those already admitted. |
|---|
| Waiting |
Places on the waiting list. These are not confirmed places. |
|---|
| Invited |
Invited places awaiting a response. This optional column is hidden by default. |
|---|
| Free |
Places still available for registration after the relevant capacity constraints. |
|---|
| Paid |
Confirmed places covered by a recorded payment. Free reservations are not counted as paid. |
|---|
| Entered |
Places already admitted. This is a cumulative entry count, not the number currently inside: exits and re-entry are not tracked. |
|---|
| Cancelled |
Historical cancellation movements, including supported quantity reductions. Older history may be incomplete. |
|---|
Do not add all columns together. Paid and Entered describe places that are already included in Confirmed. Entering the event does not consume capacity for a second time. Cancelled places do not occupy capacity and must not be added to Free again.
For example, a simple event with capacity 100, 10 organiser-reserved places and 60 confirmed places has 30 free places. If 40 confirmed places are paid and 15 have entered, it still has 60 confirmed places and 30 free places.
The symbol ∞ means there is no configured limit. An em dash (—) means a value is not applicable or not available. Free capacity alone does not mean that registration is open.
Explore programmes, events and areas
Use the expand control beside a programme or event to see its children. Expand all and Collapse all change the displayed detail without changing reservations.
Subevents can have their own dates, times, venues and areas. An area row is a breakdown of its event, not another set of bookings. Areas share the event's overall limit, so their Free values must not simply be added together. Programme capacity is not calculated by adding the capacities of its events.
Programme totals cover the events matching the current filters. A parent labelled Context only is shown to explain the structure even though it does not itself match the filters.
Find the events you need
Use the date controls and the available filters for event title, category, venue, country, state/region, county, city, publication and event status. Select Apply / Refresh to update the results. Clear returns to the view's configured defaults.
Current and upcoming is useful for daily operations. Choose All dates or another period to review earlier events. To include archived events, also change the Publication filter; changing the date range does not remove publication restrictions.
| Selected period | Single arrows | Double arrows |
|---|
| Today / Day |
Previous or next day |
Previous or next week |
|---|
| Week |
Previous or next week |
Previous or next month |
|---|
| Month |
Previous or next month |
Previous or next year |
|---|
| Year |
Previous or next year |
Not shown |
|---|
| All dates / Current and upcoming |
Disabled |
Disabled |
|---|
Open a reservation or its history
Select Registrations under an event to open its attendee list. Where available, clicking a Confirmed, Waiting or Invited count opens the corresponding filtered list. Select Movements to review registration changes if your account has access to history.
For payments and admission, use Read QR / Ticket desk. For an administrative change of area, open the reservation editor in the backend and use Change area.
Configure a frontend Tickets page
Create or edit a Joomla menu item of type JEM → Tickets. Its options let the administrator select visible filters, their defaults, visible columns, whether groups start expanded, groups per page and an optional refresh interval.
Hiding a filter does not remove its configured default. A hidden default continues to restrict the view and cannot be overridden through its URL. Filter visibility and location-column visibility are separate settings.
Automatic refresh updates the overview; it does not record payments or entries. Staff must still confirm each operation in the ticket desk.
