# The Eventlayer model (/docs/model)



Your product supplies the event page, registration form and checkout. Eventlayer
keeps the event, its attendees and their tickets connected underneath.

## Start with an event [#start-with-an-event]

**After Hours** is an event. It holds the schedule and venue. Its attendees,
ticket types and tickets belong to that event. By default, creating the event
also creates a General Admission ticket type.

## Separate the person from their access [#separate-the-person-from-their-access]

**Maya Chen** is an attendee. Her General Admission ticket is a separate record.
She could also hold a workshop ticket. Model separate admissions as separate
tickets when each one needs its own check-in.

A **ticket type** describes the access: General Admission, VIP or Staff. A
**ticket** is one instance of that access, optionally assigned to an attendee.

| Resource        | Example                | What it represents                                     |
| --------------- | ---------------------- | ------------------------------------------------------ |
| Event           | After Hours            | Schedule, venue and event context                      |
| Attendee        | Maya Chen              | A person registered for this event                     |
| Ticket type     | General Admission      | A category of access                                   |
| Ticket          | Maya’s assigned ticket | One admission, with its own lifecycle                  |
| Wallet template | After Hours branding   | Pass appearance inherited from an event or ticket type |

## Follow the ticket [#follow-the-ticket]

An available ticket becomes assigned when linked to an attendee. Check-in
records admission against that same ticket. A Wallet pass is generated from
the ticket and remains connected to it after installation.

Webhooks let your application react to changes. Your product controls email,
payment, CRM and other work triggered by those notifications.

## Choose how to configure it [#choose-how-to-configure-it]

The API and dashboard work with the same resources. Use the API when the
workflow belongs in your product; use the dashboard to configure and inspect
resources visually. The Wallet designer is useful for previewing a template.

<DocsLinks
  items="[
{ title: &#x22;Issue your first ticket&#x22;, description: &#x22;Create the example event, attendee and ticket through the API.&#x22;, href: &#x22;/docs/quickstart&#x22; },
{ title: &#x22;Understand the ticket lifecycle&#x22;, description: &#x22;Assignment, check-in and removing access.&#x22;, href: &#x22;/docs/tickets&#x22; },
{ title: &#x22;Build a complete flow&#x22;, description: &#x22;Connect these resources to the experience in your product.&#x22;, href: &#x22;/docs/guides&#x22; },
]"
/>