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

# Badges

> Print each confirmed attendee's badge — name, ticket type, and the QR code the check-in desk scans — from a fixed layout.

The Badges page prints the card the [check-in desk](/en/onsite/check-in) scans: a white card with the attendee's name, their ticket type, a QR code, and the badge code printed beneath it. Open **Onsite → Badges** after enabling the Onsite module.

## The badge code

Every registration carries a **badge code** — `CHK-` followed by a short string — from the moment it is created. There is nothing to generate and nothing to assign. The code is:

* printed on the badge and encoded in its QR code — the QR contains the bare code, nothing else, so a scanner types exactly what the desk expects;
* shown on the attendee's [entry pass](/en/events/hosted-pages) beneath the QR code, when the pass shows one;
* shown on the attendee detail page under **Check-in**;
* what an exhibitor's staff enter at the [lead desk](/en/exhibition/lead-capture) to record a visitor.

A badge code names nothing about the person and grants nothing on its own. It only resolves at a console that is already signed in, and only within its own event. Another event's code is the same "not valid" as a misspelt one.

## Who gets a badge

The page lists **confirmed** registrations only. A pending application, a waitlisted registration, and a cancelled seat have no badge and none can be printed. Once a registration is confirmed, its badge appears here.

## Print badges

<Steps>
  <Step title="Find the badges to print">
    The table lists each confirmed attendee with their email, ticket type, and badge code. Search by name or email, or filter the **Ticket type** column to print one category at a time.
  </Step>

  <Step title="Preview or print one">
    **Preview** shows the badge as it prints — event name, name, ticket type, QR code, code. **Print badge** opens the browser's print dialog for that one card.
  </Step>

  <Step title="Print all">
    **Print all (N)** prints every confirmed attendee's badge in one document, laid out as cards on A4 sheets. The browser's print dialog can save it as a PDF instead.
  </Step>
</Steps>

<Note>
  The badge layout is fixed: white card, event name on top, the attendee's name (or their email when no name was given), the ticket type, the QR code, and the code in plain text. There is no badge designer — no logos, colours, or per-ticket-type fields.
</Note>

## Rules to know

* **Badges exist for confirmed registrations only.** Confirming a registration makes its badge printable.
* **The QR code encodes the badge code**, not a link and not the registration. Reading a QR code with a phone shows only `CHK-…`.
* **One code per registration, generated automatically.** It appears wherever the registration does — on the badge, on the entry pass, on the attendee page.
* **Codes are valid in their own event only.**
* **The layout cannot be edited.** Printing is the whole feature.

## Related

<CardGroup cols={2}>
  <Card title="Check-in" icon="qr-code" href="/en/onsite/check-in">
    The desk that scans these badges.
  </Card>

  <Card title="Lead capture" icon="address-book" href="/en/exhibition/lead-capture">
    Exhibitors record visitors by badge code.
  </Card>

  <Card title="Attendees" icon="users" href="/en/events/attendees">
    Each person's badge and check-in history on their detail page.
  </Card>

  <Card title="Hosted pages" icon="panel-top" href="/en/events/hosted-pages">
    The entry pass, where the same code is shown.
  </Card>
</CardGroup>