> For the complete documentation index, see [llms.txt](https://eventx-hq.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eventx-hq.gitbook.io/knowledge-base/meetup/attendee.md).

# Attendee

As an attendee of the event, you can set up your booth, book appointments with other attendees, and manage your bookings.

## Your Actions

* [Book an Appointment](/knowledge-base/meetup/attendee/book-an-appointment.md) — Find an attendee's representative and schedule a time slot
* [Request a Meetup](/knowledge-base/meetup/attendee/request-a-meetup.md) — Book a peer-to-peer appointment (auto-confirmed)
* [Cancel an Appointment](/knowledge-base/meetup/attendee/cancel-an-appointment.md) — Cancel a scheduled booking
* [Set Up Your Booth](/knowledge-base/meetup/attendee/set-up-your-booth.md) — Add representatives, set available time slots, manage your profile
* [View and Manage Bookings](/knowledge-base/meetup/attendee/view-and-manage-bookings.md) — See all incoming bookings, accept or reject requests

## How You Access Meetup

You receive a **booking link** or **auth link** from an attendee or organizer:

| Link Type        | Purpose                                               | Example                                              |
| ---------------- | ----------------------------------------------------- | ---------------------------------------------------- |
| **Booking link** | Book an appointment with an attendee's representative | `meetup.eventx.io/appointment/{id}`                  |
| **Auth link**    | Access your own booth dashboard                       | `meetup.eventx.io/exhibitor/{id}?auth_token={token}` |

## User Roles

Everyone in the Meetup system is an **attendee** of the event. Any attendee can:

1. **Set up a booth** — add representatives, configure availability, manage vetos
2. **Book appointments** — schedule time slots with other attendees' representatives
3. **Request meetups** — peer-to-peer bookings that are auto-confirmed

## Approval Workflow

Some events use an **approval mechanism**. When enabled:

* Your booking enters a **Pending** state
* The target representative must **accept** or **reject** your request
* You receive an email when your booking is accepted or rejected

If the approval mechanism is disabled, your booking is **confirmed immediately**.