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

# Guests

> Bring guests from Luma, Partiful, The Knot, Zola, Eventbrite or a spreadsheet into one guest list per gig, and keep every guest your organization hosts in one directory.

Guests are people your gigs host: wedding guests, party attendees, comps and will-call names. Soundcheck keeps them in two places:

* **The gig's guest list.** Everyone on one gig, with their RSVP, plus-ones, meal, pass type and check-in.
* **The Guests page.** Everyone your organization has ever hosted, across every gig. A person who comes to three of your events is one guest with three gigs, not three copies.

## Where guests come from

A gig can pull guests from **several sources at once**. A wedding might link the couple's Luma event, import the Partiful list for the welcome party, and import The Knot export for the reception. Open the gig's **Guests** tab and use the sources panel:

| Source | How it works |
| - | - |
| **Luma** | Link the gig to an event on your connected Luma calendar. Soundcheck pulls the guest list right away, then keeps it current: Luma tells Soundcheck when a guest registers or changes, and Soundcheck re-checks every linked upcoming event every few hours. Luma's API needs a Luma Plus plan. Connect Luma first in **Settings → Organization → Connections**. |
| **Partiful, The Knot, Zola, Eventbrite, or a spreadsheet** | Export the guest list from the platform as a CSV or spreadsheet, then **Import list** and upload or paste it. Soundcheck reads the columns (name, email, phone, RSVP, plus-ones, meal, dietary needs, tags, notes), shows you what it found, and imports what you approve. |

To update an imported list, export it again and **Re-import** it into the same source. Guests the new file no longer lists are removed from the gig, unless someone added them by hand or changed their plus-ones or meal, another source still lists them, or they have already checked in. If a file has rows Soundcheck could not read, or you untick rows, the re-import only adds and updates.

## One person, one entry

When two sources list the same person, Soundcheck keeps one entry and shows both sources on it. It matches guests by the source's own guest id first, then by email, then by phone. A row with no email or phone matches a guest with exactly the same name, when only one guest on the gig has that name.

When sources disagree about an RSVP, the most positive answer wins: Going, then Maybe, Awaiting approval, Invited, Waitlist, and Not going. An RSVP selected when adding a guest by hand, or changed by hand later, is kept when sources sync. Plus-ones or a meal someone changed by hand stay as they set them, a party never shrinks below the guests already checked in, and a check-in never goes backwards.

## The guest directory

The **Guests** page lists every guest in your organization with their contact details, dietary needs, tags, how many gigs they have been on, how many they checked in at, and where they came from. Edit a guest there and the change shows on every gig they are on. Deleting a guest removes them from every gig.

Organization owners, admins and gig coordinators can see the directory and manage guest sources. Crew members only see and edit the guests on their own allocation.


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