> ## 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.

# Glossary

> Definitions for the people, products, and core terms you'll see across Badge.

This page defines the proper nouns and core entities you'll see across the Badge product and docs. Each term links to where the concept is explained in depth.

## Workspace and team

**Workspace**: Your team's Badge instance. Members share one billing account, one set of integrations, and one library of events, attendees, and badge templates. Switch between workspaces from the workspace switcher at the top of the sidebar. See [Create a workspace](https://docs.eventsbadge.com/workspace/create-workspace.md).

**Member**: Anyone in your workspace who isn't an Admin. Members can use Badge and the workspace integrations. Admins additionally manage billing and membership. See [Roles and permissions](https://docs.eventsbadge.com/administration/workspace/roles-and-permissions.md).

**Admin**: A workspace member with full access to billing, members, integrations, and workspace settings. Every workspace needs at least one Admin. See [Members](https://docs.eventsbadge.com/administration/workspace/members.md).

## Product

**Badge**: The on-site check-in product these docs cover. Badge designs and prints event badges and runs the mobile check-in stations your staff use at the door. See [Badge](https://docs.eventsbadge.com/index.md).

## Badge entities

**Event**: A single gathering you run check-in for. An event comes from Eventbrite or Luma, or you create it in Badge, and it carries a date range, a time zone, and a staff access code. See [Add an event](https://docs.eventsbadge.com/events/create.md).

**Attendee**: A person registered for a Badge event. Comes in via integration sync or CSV import and is the unit Badge tracks for check-in.

**Template**: The visual design Badge prints for each attendee. Includes name, company, role, photo, QR code, and any custom elements. See [Editor overview](https://docs.eventsbadge.com/templates/editor-overview.md).

**Access code**: A 6-character code (letters + digits) unique to one Badge event. Lets your check-in staff open the mobile station at `/badge/staff/<code>` without signing in to Badge. See [Access codes](https://docs.eventsbadge.com/concepts/access-codes.md).

**Booth code**: A 6-character code for one sponsor booth at a Badge event. Opens the booth's lead console at `/badge/booth/<code>`, where booth staff scan attendee badges to collect leads without signing in to Badge. See [Lead capture](https://docs.eventsbadge.com/events/lead-capture.md).

**Station**: A Badge surface for the venue. **Check-in mode** is the mobile QR scanner staff use at the door; **Station mode** is the desktop print station that auto-prints badges as attendees are checked in.

## Billing

**Pay as you go**: Badge's pricing. A workspace pays \$1.50 per check-in, billed monthly, with no monthly fee. See [Pricing](https://docs.eventsbadge.com/administration/billing/pricing.md).

**Check-in**: The billed unit. An attendee counts once for each event day staff check them in. See [Usage](https://docs.eventsbadge.com/administration/billing/usage.md).

## Integrations

**Integration**: An external account connected to Badge through OAuth. **Eventbrite** and **Luma** sync events and attendees into Badge. Connect them from **Workspace → Integrations**. See [Eventbrite connect](https://docs.eventsbadge.com/integrations/eventbrite.md) and [Luma connect](https://docs.eventsbadge.com/integrations/luma.md).

## Related

* [Events, attendees, templates](https://docs.eventsbadge.com/concepts/events-attendees-templates.md). The Badge entities in depth.
* [Badge quickstart](https://docs.eventsbadge.com/quickstart.md). Add an event and check in your first attendee.


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