Appearance
Admin Screens
Voxel Events adds an Event Tickets menu to the WordPress admin with four screens.
| Screen | Capability | Who typically uses it |
|---|---|---|
| Check-in | edit_posts | Door staff and event authors |
| All Tickets | edit_posts | Event authors reconciling sales and attendance |
| Oversold | edit_posts | Event authors and admins checking for events that went over capacity |
| Settings | manage_options | Administrators only |
Event authors don't need admin access
Check-in also works from the front end through the Event Check-In widget, which is usually a better fit for door staff on a phone. Authorisation is author-based, so Voxel custom roles work without the edit_posts capability.
Check-in
The default screen. Scan or enter a ticket code to check an attendee in.
See Event Check-In Widget for the front-end equivalent and the check-in workflow.
All Tickets
A searchable list of every ticket issued on the site.
Filters
- Event — narrow to a single event, or All Events
- Status — Checked In, Not Checked In, or All Statuses
The screen shows a running count of matching tickets, and a Clear button to reset filters.
Columns
| Column | Contents |
|---|---|
| Code | The ticket code, in your configured PREFIX-XXXXXX format |
| Attendee | Name and email captured for the ticket |
| Event | The event the ticket belongs to |
| Status | Checked In, or Pending |
| Order | Link through to the originating order |
| Created | When the ticket was issued |
| Actions | Per-ticket actions |
Free tickets may have no attendee details
Paid tickets capture the buyer's name and email at checkout. Free tickets skip checkout entirely, so the Attendee column is empty unless the event collects name and email through the Attendee Information section — see Settings.
Oversold
Orders that completed for more tickets than the date had left. Added in 1.2.0.
The tickets in these orders were issued — the customer had already paid — so this is a record to act on rather than a queue to approve. It exists so an oversell cannot pass unnoticed until the guests arrive.
Columns
| Column | Contents |
|---|---|
| Event | The event, linking to its editor |
| Tickets Affected | Each date and ticket type that went over, with quantity ordered and how many were over |
| Over By | Total tickets beyond capacity for that order |
| Customer | Name and email captured at checkout |
| Order | Link through to the originating order |
| When | When the order completed |
Filter by event when more than one has oversold. The summary line above the table totals the orders and the tickets beyond capacity for whatever is currently filtered.
Authors only see their own events
Site administrators see every conflict on the site. Event authors see only conflicts on events they own, so the screen is safe to leave reachable on a multi-venue site.
An empty screen means no event has sold beyond capacity, which is the normal state.
See Overselling & Capacity for how conflicts arise, the notification, and the setting that most reduces them.
Settings
Site-wide configuration — ticket codes, wallets, email batching, cart reservation, capacity conflicts, service fees, and which sections appear in the create-event form.
See Settings for every option.