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

# Events

> Manage genuine conferences, webinars, workshops, training sessions, and registrations.

## What Events is for

Events is the Engage calendar for scheduled sessions: conferences, webinars, workshops, trade shows, meetups, reviews, training, and meetings. Quarterly Business Review documents are presentations and now live in **Engage → Presentations**.

The page shows Total Events, Upcoming, Featured, and Registrations. Search and date sections operate only on event records; presentation records do not affect these counts.

## Creating an event

<Steps>
  <Step title="Open Events">
    Open **Engage → Events**, then select **Create Event**.
  </Step>

  <Step title="Add the schedule">
    Enter a title, description, start and end dates, event type, location, expected attendance, and an optional registration URL and thumbnail.
  </Step>

  <Step title="Choose visibility in the list">
    Mark an important event as Featured to pin it above the date-grouped event list.
  </Step>

  <Step title="Save">
    Select **Create Event**. The event appears in the appropriate date section and updates the event counters.
  </Step>
</Steps>

<Info>
  To create or edit a QBR document, use **Engage → Presentations → QBRs**. A scheduled QBR meeting and its presentation are separate concepts.
</Info>

## Opening an event

An event detail shows its dates, status, description, location, registration count, expected attendance, and registration link. Existing bookmarks for older event-backed QBR documents are automatically resolved to the corresponding presentation.

## Next

<CardGroup cols={2}>
  <Card title="Presentations" icon="presentation" href="/engage/presentations">
    Create and manage QBRs and client-ready presentation artifacts.
  </Card>

  <Card title="Adoption" icon="trending-up" href="/engage/adoption">
    Track whether training events translate into module usage.
  </Card>
</CardGroup>