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

# Guests

> Check a name against the guest list, admit guests at the door, and add someone who was approved on the day.

The **Guests** workspace is for invite lists. Use it to check a name against the list, admit the guest, or add someone who was approved on the day. Open it from the [Command Center](/onsite/command-center).

## Find a guest

Search by **name or email** and select **Search**. The list shows 25 guests per page; use **Previous** and **Next** to move through it.

| Column | Meaning |
| - | - |
| **Name** | The guest's full name. |
| **Email** | Their email, or a dash if none is on file. |
| **Entry** | **Checked in** or **Not checked in**. |

> [!WARNING]
>
> A name is not an identity. If more than one guest could match, the row shows a warning note under the name. Confirm who the person is before you admit them. Don't admit on a name match alone.

## Admit a guest

Select **Check in** on the guest's row. No reason is needed, because admitting is ordinary work at the gate. A confirmation message appears and the row updates to **Checked in**.

## Undo a check-in

If a guest was checked in by mistake, select **Undo check-in** on their row. A side panel opens, naming the guest, and explains:

* **What will happen:** this guest-list entry can be used again.
* **What will not happen:** the original admission stays in the activity log.

Choose a **Reason** from the list (required), add an optional **Note**, and select **Confirm**. Undoing needs a reason because it is a correction and has to be explainable afterwards.

## Add an approved guest

Select **Add an approved guest** to add someone who wasn't on the list but was approved. Fill in:

| Field | Required | Notes |
| - | - | - |
| **Full name** | Yes | As they'll give it at the door. |
| **Ticket type ID** | Yes | Which ticket type this guest counts as. Get it from [Ticket management](/tickets/ticket-management). A guest still counts against a ticket type. |
| **Who approved this?** | Yes | For example "Approved by the promoter by phone, 20:15". It is stored with the action, because without it nobody can tell afterwards whether the addition was authorised. |

**Add guest** stays disabled until all three are filled in. The addition is recorded with the reason "Approved guest addition".


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