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

# Connect Luma

> Connect Luma once, then import events and attendees into Badge, and manage the connection from Workspace → Integrations.

The Luma integration links your Badge workspace to one Luma account. Once connected, anyone in your workspace can import a Luma event into [Badge](https://docs.eventsbadge.com/index.md) in a single click. No CSV exports, no manual uploads. Badge brings in the event and every registrant.

> [!NOTE]
>
> **Before you start**
>
> * A Luma account that owns or has access to at least one event.
> * A Badge workspace with billing set up. See [Pricing](https://docs.eventsbadge.com/administration/billing/pricing.md).

## Connection model

* **One Luma account per workspace.** To switch accounts, disconnect the current one and connect the new one.
* **Workspace-scoped.** The connection belongs to the workspace, not to the member who connected it.

Connecting gives Badge read access to your Luma account. What Badge receives:

* **Read access to your events**: name, start and end time, timezone.
* **Read access to your guests**: every field you collect on the Luma registration form.

Badge cannot post or edit anything in your Luma account.

## Connect

**1. Open Workspace → Integrations**

Sign in at [eventsbadge.com](https://eventsbadge.com), click **Integrations** under **Workspace** in the sidebar. You'll see a card for each supported provider, including Luma.

![Integrations page with an Eventbrite card and a Luma card, each with a Connect button](https://mintcdn.com/eventsbadge/sVLPHidr7TFp4nzL/images/screens/integrations.png?fit=max\&auto=format\&n=sVLPHidr7TFp4nzL\&q=85\&s=41806137288b9739f374f56e0ea11866)

Workspace → Integrations

**2. Click Connect on the Luma card**

Click the **Connect** button on the Luma card. Badge opens the Luma connection dialog.

**3. Complete the Luma connection**

Fill in the connection dialog and submit it. Badge returns you to **Workspace → Integrations** when the connection is ready.

**4. Confirm the connection**

Back in **Workspace → Integrations**, the Luma card now shows a green **Connected** badge with the email of the member who connected it and the connection date. You're ready to import.

**5. Import a Luma event into Badge**

Open **Events** in the sidebar and click **Import Event** in the page header. Pick **Luma** in the provider picker, then click **Import** next to the event you want. Badge imports the event and its attendees. See [Add an event](https://docs.eventsbadge.com/events/create.md) for the full dialog.

## What syncs

When you import a Luma event, Badge brings in:

* The **event itself**: name, start time, end time, and timezone.
* Every **attendee**: email, name, and the fields Luma collects during registration.

## Status states

The Luma card on **Workspace → Integrations** is in one of three states:

* **Not connected.** The card shows a **Connect** button. Click it to start the connection.
* **Connected.** A green **Connected** badge appears in the top right, with the email of the member who connected it and the connection date underneath. The card has an external link to Luma and a **Disconnect** button.
* **Reconnect required.** An amber **Reconnect required** badge replaces the green one. The card description reads: *"Authentication expired or revoked. Connect a new Luma account, then remove this entry."* This state appears when the Luma credential stops working, for example after the Luma account owner rotates or revokes it in Luma's settings.

## Reconnect

When the card shows **Reconnect required**, Badge keeps the disconnected entry visible so you can finish the cleanup deliberately. Click **Connect** on the Luma card that offers it (not the disconnected entry), run through the Luma connection again, then click **Remove** on the disconnected entry once the new connection is in place. Events and guests you already imported stay in your workspace through the disconnect.

## Disconnect

On the connected Luma card, click **Disconnect**. A confirmation dialog opens with the message: *"This will remove the connection to your Luma account. You can reconnect at any time, but you'll need to re-import your events."* Confirm to flip the card to the not-connected state. Already-imported events stay in your workspace; new Luma events won't appear until you reconnect.

## Troubleshooting

### The Luma card shows "Reconnect required"

The Luma credential stopped working or was revoked from the Luma side. Click **Connect** to reconnect Badge, then remove the disconnected entry. Full pattern: [Reconnect](#reconnect).

### An event I expected to see is missing from the import dialog

Check that the event is owned by (or shared with) the Luma account you connected. If you have multiple Luma accounts, disconnect and reconnect with the right one.

## Related

* [Connect Eventbrite](https://docs.eventsbadge.com/integrations/eventbrite.md). Same flow for Eventbrite.
* [Upload attendees from a CSV](https://docs.eventsbadge.com/events/upload-csv.md). The manual import path.
* [Import attendees into Badge](https://docs.eventsbadge.com/events/import-attendees.md). Using the same connection to populate a check-in event.
* [Recovering from disconnect](https://docs.eventsbadge.com/events/recovering-from-disconnect.md). What happens to a Badge event when its integration goes into the reconnect state.


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