> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eventsbadge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events, attendees, templates

> The three core entities in Badge and how they relate.

> [!NOTE]
>
> Badge organizes Badge check-in around three entities: an **event** holds a list of **attendees**, synced from your provider or uploaded as a CSV, and a set of **templates** decides what each attendee's printed badge looks like.

Badge is built around three entities. Every check-in, every printed badge, and every staff station you set up traces back to one of them. These three entities underlie imports, templates, and staff handoff.

## Events

An **event** is a single gathering. Each event has a name, a date range, a timezone, a source, and a 6-character access code for staff. The source is an integration provider (Eventbrite or Luma), with a sync status that says whether attendee data is flowing, or Badge itself (**Manual**) for an event you create.

You bring an event in from a connected provider with **Import Event**, or make one with **Create Event**. Either way, the event lives on the Badge dashboard with stats, a staff access card, and a templates section.

Example: `Q2 Customer Day` on May 22 in San Francisco, imported from Eventbrite, sync status `ACTIVE`, access code `K9F2QT`.

## Attendees

An **attendee** is one registration on one event. Each attendee carries an email, optional name fields, company and job title, a ticket name (the ticket type they bought), a barcode, a VIP flag, and a check-in timestamp once they arrive.

On an imported event, attendees stream in as the import job runs and continue updating while sync is `ACTIVE`. New registrations, cancellations, and field edits made on the provider side flow through automatically. On an event you created, attendees come from your [CSV uploads](https://docs.eventsbadge.com/events/upload-csv.md), and a walk-in added at the check-in desk becomes an attendee too. Staff check in attendees from the mobile station; VIPs are flagged so you can spot them in the attendee table and filter to them at the staff station.

Example: Maya Chen, `maya@northwind.io`, ticket `Founder Pass`, VIP, checked in at 9:14 AM.

## Templates

A **template** is the printed badge layout for an event. Each event starts with a **Default badge** that prints for every ticket type no variant claims (the templates page marks it **Fallback**), and you can add **variant** templates that apply to specific ticket types. For example, a different layout for `Founder Pass` versus `General Admission`. Each ticket type belongs to one template, so assigning a ticket to a new variant moves it off the old one. A variant left with no tickets shows **No tickets assigned** and prints for nobody until you assign one.

Templates are designed in the visual editor: text, image, QR, and rectangle elements positioned on the label. Text elements can be bound to attendee fields (full name, company, job title, ticket name, barcode), so the same template renders correctly for every attendee.

Example: a Default badge with a logo, the attendee's full name in 14 mm type, company in 6 mm type, ticket name in a colored bar, and a QR with the attendee's barcode.

## How they relate

An event contains attendees, and every event has a Default badge. When a staff station prints, Badge matches the attendee's ticket type ID (on an event you created, the **Ticket Type** value from your CSV) against each variant's assigned tickets, then falls back to the Default badge. Matching on the ticket type ID keeps variants attached after you rename a ticket type on the provider.

```
Event  ──►  Attendees  ──┐
  │                       ├──►  Printed badge
  └────►  Templates  ─────┘
              │
              ├── Default (all tickets)
              └── Variant (assigned tickets)
```

## Related

* [Access codes](https://docs.eventsbadge.com/concepts/access-codes.md). How staff get into a mobile station without signing in.
* [Sync status](https://docs.eventsbadge.com/concepts/sync-status.md). What `PENDING` / `ACTIVE` / `FAILED` / `DISCONNECTED` mean for an event.
* [Add an event](https://docs.eventsbadge.com/events/create.md). Import an event from a provider, or create one in Badge.
* [Editor overview](https://docs.eventsbadge.com/templates/editor-overview.md). The visual template editor.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.