Glossary

Core

Add-on: An optional extra a person can add to a ticket, during registration or later, subject to availability. You organise add-ons into groups you define, each with its own rules for how many can be chosen and which apply. Add-ons can be free or paid, with limited or unlimited stock. (The detailed group rules live in the Ticketing docs.)
Badge: The credential a ticket-holder receives at check-in, used to identify them at your event. A badge can be a printed card, a sticker, a wristband, or another format you choose. The "badge name" is the name shown on it.
Booking Type: The category of ticket a person chooses first when registering. Each booking type has its own price, sale dates, availability, and eligibility. Examples: Early Bird, Standard, and Premium for a party; Bunkroom, Cabin, and Villa for a camp.
Check-in: The on-site process when a person arrives at your event: confirming their ticket and handing over their badge and any items they ordered. Check-in is the in-person counterpart to registration.
Environment: Where your EventDrake data is hosted: a specific regional location (for example, Australia) that determines where your data is stored. It is fixed for your site; changing it means setting up a new site. This mostly matters for questions about data residency.
Event: A single ticketed offering that people register for: one camp, one party, one conference, or one run of a show. Your site usually runs many events, and each is normally used once and then archived rather than reused (an annual festival creates a new event each year). Each event has its own page on your site, for example example.com/summercamp. When your site has only one active event, EventDrake automatically presents it as the site's main page and keeps the multi-event navigation out of the way.
Fallback Domain: The default web address EventDrake provides for your site. It always works, and is available before you connect your own custom domain (and as a backup afterwards). It uses a system-generated site identifier followed by .edhosted.net, for example a1b2c3d4-....au-a.edhosted.net. The identifier is a unique code, not your site's name. You can also point your own domains at your site.
Markdown: A simple way to format text by typing a few plain characters, for example ** around a word to make it bold. Description fields across the admin accept Markdown, plus a few common extras such as tables. Text works fine without it; you add formatting only where it helps.
Merch: Physical items included with a ticket or bought alongside one, such as t-shirts, prints, or other goods. (Handled in the Merch docs.)
Order: A single purchase placed at one point in time, such as one or more tickets and any add-ons bought together. Each order is placed by one person, who is normally also the one paying, and has its own invoice number. When one person registers several people at once (for example, a parent booking for their children), that is still a single order and one bill covering everyone in that booking.
Question: A single prompt with an answer of a chosen kind: a text box, a number, a checkbox, a dropdown, a date, and more. Questions are a shared building block used across EventDrake, for example on registration forms and at check-in. Each question has an input type (how it is answered) and a render type (how the saved answer is shown).
Question & Answer: EventDrake's system for collecting information from people through questions you define, with each answer saved against the relevant record. You can ask questions during registration (against a ticket or the whole order, and triggered by a chosen booking type or add-on), as a standalone survey, or inside other tools such as on-site check-in. Ticket Questions are one common use: questions asked of each ticket-holder during sign-up (covered in the Ticketing docs).
Registration: The sign-up process a person completes to get a ticket: choosing a booking type, answering any questions, adding add-ons, and paying. This happens online, before the event. In the admin, the area where you set up and manage all of this is labelled Registration; it is sometimes also referred to as Ticketing, and both names mean the same part of the product.
Room: A shared space attendees are grouped into, such as a cabin, dorm, table, or accommodation room, with a capacity for how many it holds. A room is created automatically when someone books a booking type set to create a room for each booking, or by hand when you allocate individual attendees to spaces. Room management is turned on per event.
Saved Booking: A person's full registration details saved in advance rather than submitted, optionally with a saved card or a held payment. It is used three ways. Pre-Fill: before registration opens, people enter their details in advance (and, close to opening, hold their payment) so they can submit the moment tickets go on sale. Waitlist: after a booking type sells out, people leave their details (optionally with a card) so you can offer them a place if one frees up. Saved for later: while registration is open, a person saves their booking to finish later. You can work through pre-fill and waitlist queues from the admin area.
Site: Your organisation's whole presence in EventDrake: your events, your users, your data, and the settings behind them, reached through one or more web addresses you control (plus a fallback domain EventDrake provides). Your plan and billing are set here. One organisation can run more than one site: a common example is a separate testing site, which cannot take real payments or issue real tickets but lets you trial design or event setup before changing your live site. (More technical users may know a site as a "tenant"; we use "site" in these docs.)
Site Config: Where your site's settings live in the admin, gathered in one place and grouped into sections by the part of the product they affect. Most settings have a site-wide default and can be overridden for individual events; a few are managed by EventDrake and shown as read-only.
Ticket: A single booking for one person to attend an event. One person can hold several tickets, for example a parent booking for their children. Most things attach to a ticket rather than to a person: add-ons, questions, and check-in. Every ticket belongs to exactly one booking type.
URL Key: The short, web-friendly name that sets where something lives in a web address, made of lowercase letters, numbers, and hyphens. Each event has a URL key: an event with the URL key summercamp appears at example.com/summercamp. URL keys are used across EventDrake wherever something needs a stable, readable address.
User: A person with an account on your site, usually an attendee who signs up, buys tickets, or manages their own bookings. A user has profile details such as name, email, phone, date of birth, preferred name, and a default badge name.

Check-in and operations

Badge Template: The design used to produce a badge: what appears on it and where, for a given kind of ticket. Badge templates are set up separately; check-in uses them to print the right badge for each attendee.
Barcode Scanner: A device that reads a printed barcode or QR code and types its value, used to look up an attendee from a ticket code or to confirm a badge or picklist. Most plug in over USB and need no setup.
NFC: A short-range wireless chip that can be built into a badge and read by tapping it on a reader. EventDrake can write an attendee's details onto the chip during check-in. What gets written is set by an NFC template.
NFC Template: The setup that decides what is written to a badge's NFC chip during check-in, such as the attendee's details or a link. NFC templates are created separately; check-in uses them to write the right data to each badge.
Operator: A staff member or volunteer running a station on the day. Operators usually sign in with a temporary session rather than a full admin account, and only see the tools their station needs.
Peripheral: A piece of hardware attached to a terminal, such as a badge printer, a receipt printer, an NFC reader, or a barcode scanner. A peripheral belongs to the terminal it is plugged into; other desks use it by pointing at that terminal.
Print Server: A terminal whose only job is to host one or more shared printers, often running headless with no operator. Print servers suit a single, more expensive printer (such as a plastic-card printer) that several desks share.
Receipt Printer: A printer for narrow paper receipts and merch picklists, usually connected over a serial USB link. Unlike a badge printer it must be configured before use, including its paper width and how it cuts.
Register: A point-of-sale till used to take payment at a station, with its own record of takings. A desk that only checks people in does not need a register; a desk that also sells does.
Station Profile: A saved setup for one kind of check-in desk. It decides what an operator sees and does at that station: which tools appear, whether badges print automatically and to which printer, and which queue the station works from. You create a profile once and reuse it on every desk of that kind.
Temporary Session: A short-lived sign-in that lets a volunteer or staff member run a station without a full admin account. An administrator approves each request, choosing which events the person can work and for how long, and the session then expires on its own.
Terminal: A physical device running EventDrake's on-site software, such as a check-in tablet or a countertop unit. A terminal can have hardware attached, for example a badge printer, a receipt printer, or an NFC reader. Terminals are registered once, then paired to a station at the start of a shift.
Ticket Queue: A named group that tickets are placed in so you can direct people to the right check-in desk, for example General, Priority, or Escalation. A queue is a label and a grouping, not a physical line: you decide which tickets go in it and which desks work from it. A ticket can be moved between queues by a rule or by an operator.

Merch

Fulfillment: Marking an ordered item as handed to the attendee. At the merch table an operator fulfils each item, or scans a picklist to fulfil them all at once, so you have a record of what has been collected.
Included Merch: A merch item that comes bundled with a booking type or add-on, given as part of the ticket rather than bought in the store, such as a shirt that comes with a weekend ticket. Set up per event, it is added to a ticket automatically when someone books a matching booking type or add-on, and collected at pickup like any other merch.
Merch Pickup: The on-site step where an attendee collects the merch included with or bought alongside their ticket. Pickup usually happens at a dedicated merch table, prompted during check-in when the attendee has items to collect.
Picklist: A printed list of the merch an attendee has ordered, used at the merch table to gather and hand over the right items. A picklist can print automatically when an attendee is sent to the merch queue.

Calendar

Agenda: An attendee's own list of calendar entries, reached from My Agenda on your site. Entries arrive there when the attendee favourites them, and when a roster shift is published for them. Reminders are sent for favourited entries only.
Background Band: A calendar entry drawn as a wash of colour behind the sessions rather than as a session card of its own. Bands mark a span of time rather than something to attend, for example the hours a dealers room or bar is open.
Calendar: A published programme for an event: sessions and other items laid out across dates and times for attendees to browse on your site. An event can have several calendars, for example a main session schedule alongside a guide to event spaces, and each has its own web address. A calendar is only shown to attendees once you make it visible.
Calendar Entry: One item on a calendar, such as a panel, workshop, or performance. It has a name, description, artwork, and a start and end time, and can be assigned to a lane. The same entry can be attached to more than one calendar, so a headline session can appear on both a main schedule and a room guide without being entered twice.
Lane: A named, colour-coded grouping inside a calendar, such as a stage, room, or track. Lanes colour the entries assigned to them in every display mode, and become the columns in the lanes grid. Lanes are set up on the calendar itself, so each calendar has its own set.

Email

Email Template: One of the emails your site sends, such as a registration confirmation or a password reset, made up of a subject and a designed body. Built-in templates send automatically when something happens, like an order being placed or a password reset being requested. You can customise the wording and design of these, and you can also create your own custom templates to send to people by hand.
MJML: The email markup language EventDrake templates are written in. It is designed to produce emails that display correctly across the many different email apps people use. Customising a template's design means editing its MJML, which is similar in feel to editing web page markup.
Placeholder: A marker you drop into an email template that is replaced with a real detail when the email is sent, such as the recipient's name or the event title. The editor's Variable button lists the placeholders available for the email you are editing and inserts them for you, so an email can be written once and personalised for every recipient.

Orders

Credit Note: A record of value taken off an order after it was placed, for example when an item is cancelled or refunded. It shows how much came off what the customer owed, and how much (if any) was returned to them. A credit note is created automatically whenever you cancel or refund part or all of a paid order.
Invoice: The billing record for an order. Every order has a single invoice, with its own invoice number, covering everyone and everything booked together. Payments and refunds are tracked against it, so the invoice is the running record of what was owed and what has been paid.
Line Item: A single line on an order, such as one ticket, an add-on, a merch item, a dealer purchase, or a custom charge. Each line has its own price, quantity, and status, and the lines together make up the order's total. An item can be cancelled or refunded on its own without affecting the rest of the order.
Payment: A record of money received against an order, such as a card charge, a bank transfer, or cash taken at the door. An order can have several payments. When they add up to the order total, the order is fully paid; until then it is partly paid.
Payment Authorisation: A temporary hold placed on a card that reserves the money without taking it yet. It is captured (actually charged) when the order is approved. A hold is only good for a few days: if it is not captured in time it lapses, and payment then has to be collected another way.
Refund: Money returned to a customer for all or part of an order. Card payments taken through the platform can be refunded automatically; payments made another way, such as bank transfer or cash, are returned by hand and recorded against a credit note.
Voucher: A code a customer enters at checkout to get a discount on specific items, or to unlock an item that is otherwise unavailable to them. A voucher applies to the booking types, add-ons, or merch you choose, not to the whole order. It can be a single shared code or a set of unique single-use codes.

Rostering

Assignment: One person placed into one position on one shift. An assignment covers either a ticket holder or an external person, never both. Published assignments appear on the person's agenda and trigger their shift reminders.
Eligibility: The ticket tags a position expects someone to hold, matched either as all tags or any tag. Eligibility guides who the system suggests for a position, but never blocks you: assigning someone who does not match is allowed and simply records that the requirement was overridden.
Group: A named, colour-coded set of shifts within an event, such as Ops, Registration, or Bar. Groups are how the roster is divided up: each one becomes a lane on the roster calendar, and you can set a planning status across a whole group at once.
Position: A role needed on a shift, such as First Aider or Door. A position carries how many people it needs, which ticket tags make someone eligible, and the list of people assigned to it. A shift with no positions cannot hold anybody.
Shift: A block of time that needs to be staffed, with a label, an optional location, and a start and end. A shift belongs to one group and holds one or more positions. Shifts are capped at 24 hours and must fall within a week either side of the event dates, which leaves room for setup and teardown.

Users and access

Role: An area of access you grant to a person, such as running registration or editing your website. Roles are built in: each one opens a set part of the product. You grant roles to people, and remove them to take access away, but you do not configure what a role can do. A role is either global (applying across your whole site) or event-specific (granted for one event).
Single Sign-On: A way for people to sign in to your site using an account they already have with an outside provider, such as a company login or a social account, instead of a separate password. Single sign-on is set up with EventDrake rather than switched on from the admin area.
Tag: A label you put on a ticket to mark and group it, without changing what the ticket is or costs. Tickets can be tagged automatically by their booking type, an add-on, or a voucher, or by hand. Tags are then used to filter tickets, drive rules, and choose which badge prints.

Website and content

Content Block: A small piece of content you add into a fixed spot on one of EventDrake's built-in pages, such as a note above the registration form or an image in the footer. You fill the spots EventDrake provides rather than creating new ones. A block can be set once for the whole site and overridden for a single event where needed.
Custom Page: A content page you write yourself and publish on your site, such as an About, venue, or privacy page, each at its own web address. Custom pages are separate from the pages EventDrake builds for you, such as registration or the homepage. A site-wide page sits at the top level (example.com/about); an event page sits under its event (example.com/summercamp/venue).
Theme: A saved set of visual choices, colours, fonts, and corner style, that sets how your public site looks. You build a theme on top of one of the built-in base themes and can add your own styling. A theme applies to your whole site by default and can be overridden for individual events.
Website: The area of the admin where you build and design your public site: your homepage, custom pages, menus, content blocks, files, and themes. It is grouped in the admin under Website / CMS. "CMS" (content management system) is another name you will see used for the same area.