> ## Documentation Index > Fetch the complete documentation index at: https://docs.vidimo.app/llms.txt > Use this file to discover all available pages before exploring further. # Check guests in > Check in the guests who are actually at the desk, send their registration in one go, and check in anyone who arrives later as a check-in of their own. A check-in is a group of a booking's guests who arrive together. You record it when they are in front of you: tick who is here, scan anyone missing, and send. Vidimo records the check-in, marks the booking **Checked In** the first time, and sends those guests to your guest-registration authority straight away, as one submission where the authority takes a family or group together. A booking nobody is on yet has nobody to tick: its button checks the booking in on its own. Anyone who arrives later, a partner who joins the next day, is a check-in of their own. A guest who is on the booking but never comes is in no check-in. ## Check guests in **1. Open the check-in** At an **In person** property, tap **Check in** beside the status on the [reservation](https://docs.vidimo.app/reservations/view-a-reservation.md). On [Today](https://docs.vidimo.app/today.md), tap **Check in** on the arrival's row to open the reservation first. At a **Self check-in** property, that button checks the booking in on the tap, offline too, and the check-in opens from **Check in a later arrival** (see [Who checks guests in](#who-checks-guests-in)). **2. Tick who is here** The **Who's here** list shows the booking's guests who are not checked in yet, each with their ID status. Nobody is ticked to start with: tick each person standing at the desk. A guest with no ID on file has **Scan ID** on their own row: it scans their document for them, and they come back ticked. A guest whose arrival is already reported, cancelled or held up shows a **Report to** line saying where it stands: this check-in doesn't send it again. **3. Add anyone missing** **Scan ID** reads a passport or ID card, and **Type ID** lets you enter it by hand. When you come back, the people you ticked are still ticked, and someone you added joins the list already ticked. See [Scan a guest ID or passport](https://docs.vidimo.app/check-in/scan-guest-id.md). **4. Send** Where your property reports guests to an authority, the button reads **Check in and send to** followed by its name, for example **Check in and send to Alloggiati Web**. It stays greyed out until every ticked guest has an ID on file, and the line above it names who is missing one. If the authority needs an ID for this stay that the app doesn't show yet, sending says whose to scan. Elsewhere it reads **Check in**. Sending needs a connection: the button says so when your phone is offline. A booking can be checked in from its arrival day. The screen then becomes the check-in's record: when it happened, who checked the guests in, and for each guest their ID status, such as **ID on file**. Where the stay is reported, a **Report to** line under it says where their report stands as the authority answers, for example **Registered**. **Check in more guests** starts the next check-in for anyone on the booking still waiting. ## Later arrivals Once a booking is checked in, the reservation lists its **Check-ins**, each with its time and how many guests it holds; tap one to open its record. While someone on the booking is still waiting, **Check in a later arrival** below the list starts a new check-in for them. The first check-in is reported as arriving on the booking's arrival day. At an **In person** property, a later check-in is reported as arriving on the day it was recorded, or on the arrival day if it was recorded on or after the check-out day. At a **Self check-in** property, a guest is registered on the booking's arrival day as soon as their ID is on file, so scanning a later arrival sends them before you tap **Check in**. A guest who came but was never checked in can still be checked in after the booking has checked out, so their registration goes out. A register can refuse an arrival sent that late; if it does, register them on the authority's own site and tap **Mark as filed manually** on the filing. ## Who checks guests in Each property says who checks its guests in. You'll find it in the property settings, under **Guest portal**, as **Check-in**, just below **Access method**. * **Self check-in**: guests check themselves in. **Check in** beside the reservation's status checks in everyone on the booking not checked in yet, and a guest nobody checks in at the desk is still registered on the booking's arrival day, as before. * **In person**: staff check every guest in. A guest nobody checks in is never registered automatically, so a companion who never comes is never reported. A guest who adds their details in the guest portal is told they are saved and that they'll be checked in when they arrive. Their registration reads **Not checked in** until they are. The **Edit reservation** form doesn't offer **Checked In** or **Checked Out** for a stay nobody has checked in yet: use **Check in**. At an **In person** property, if a guest is still not checked in 3 hours before their registration deadline, everyone on the property who can edit guests gets a push, **Guest not checked in**: check them in if they came. A guest who never came is never reported. > [!NOTE] > > Properties that already used **Staffed reception** when this setting arrived > were set to **In person**. A new property starts as **Self check-in**, and > changing the access method leaves **Check-in** as you set it. Changing **Check-in** also applies to stays in the house now, as well as those to come: * Switching to **In person** counts everyone on them as checked in, as **Self check-in** did. * Switching to **Self check-in** counts anyone on them still not checked in as having stayed, and registers them. A stay that has already left keeps the setting it had while the guests were there: who stayed, what was registered and the tourist tax stay as they were. ## Undo a check-in Setting the booking back to **Confirmed** from the **Edit reservation** form removes its check-ins. Once a check-in's guests have been sent to the authority, the app says the booking can no longer go back to before check-in. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.