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

# Check-in steps

> Use verification rules to pick which check-in steps each guest gets: ID check, agreements, damage waivers, deposits, fees, guest details, questions and more.

Verification rules decide which check-in steps a portal shows. Each rule is one step plus the stays it targets. With no rules, portals have no check-in steps. Templates don't set check-in steps.

## Create a rule

Needs **Manage Portals**.

1. Go to **Portals > Verification > Rules** and click **New rule**
2. Fill in **Name** (internal) and pick the **Step**. The step can't change after the rule is created
3. Fill in **Title** (what the guest sees) and the [step settings](https://docs.conduit.ai/portals/step-settings.md)
4. Set **Targeting**, or leave it blank to cover every stay
5. Click **Create rule**

* New rules are enabled straight away and go to the bottom of the list
* **Test in sandbox** opens the [sandbox](https://docs.conduit.ai/portals/test-and-go-live.md#sandbox) with the rule as it is in the editor, saved or not

## Step types

| Step | What the guest does | Matching rules |
| - | - | - |
| **ID check** | Uploads an ID, plus a selfie if you ask for one | First one wins |
| **Agreement** | Reads and signs a document | All apply |
| **Damage waiver** | Signs a waiver, and pays when it's priced | First one wins |
| **Security deposit** | Saves a card for a refundable hold | First one wins |
| **Required fee** | Pays a fee | All apply |
| **Your details** | Fills in contact and arrival details | First one wins |
| **Questions** | Answers your questions | All apply |
| **Additional people** | Adds the other people on the stay | First one wins |
| **Chekin guest registration** | Registers every guest through Chekin | First one wins |
| **Custom gate** | Nothing. It completes when its conditions match | All apply |

* "First one wins" means the highest matching rule in the list applies and the rest of that step type are skipped
* A matching damage waiver and security deposit become one step, **Choose deposit or waiver**. Either one completes it
* Every matching required fee is paid together as one step
* Guests see the steps in this order and can do them in any order: agreements, waiver or deposit, ID check, Chekin, fees, your details, questions, additional people, custom gates
* The rule list and Submissions call **Your details** "Guest details"

## Targeting

All filters must match. A stay with no value for a filter fails **Include** and passes **Exclude**.

| Filter | What it matches |
| - | - |
| **Booking channels** | **Include** or **Exclude** the channels you pick. Stays with no channel count as **Unknown** |
| **Reservation sources (advanced)** | **Include** or **Exclude** exact PMS source values, like owner stays. Matching is case-sensitive |
| **Min nights**, **Max nights** | Stay length |
| **Check-in days** | Weekday of the arrival date |
| **Booking date** | When the reservation was created: **Before**, **On or before**, **On**, **On or after** or **After** a date, in the workspace time zone. Stays with no booking date don't match |
| **Booked within** | Reservations created this many days or fewer before check-in. **Apply when booking time is unknown** also matches stays with no booking date |
| **Listings**, **Listing groups** | A listing you pick, or one in a group you pick |
| **Bedrooms**, **Bathrooms** | **Exactly** or a **Range**. Listings with no count don't match |
| **Custom attributes** | Contact attribute values when the portal is sent, up to 20 conditions |
| **Skip returning contacts** | Contacts without a past completed stay |
| **Only when the guest answers** | Required fees only. Answers to choice questions in a **Questions** or **Your details** rule higher in the list, up to 20 conditions |

## Order, switch off and delete

The **#** column is each rule's priority, with 1 at the top.

* Drag a row, or use **Move up** and **Move down** in the **⋯** menu
* The **Enabled** switch saves right away, with no confirmation
* **Delete** in the **⋯** menu can't be undone. Guests who started its step keep it
* There's no duplicate
* A question rule used by a fee's **Only when the guest answers** can't be switched off, deleted or moved below that fee

## Changes reach portals already sent

Every rule change counts: creating, saving, switching, reordering and deleting.

* Portals update within a few minutes of the latest change
* A stay updates right away when its reservation changes on a PMS sync
* Steps the guest hasn't started follow the new rules. A step the guest started keeps the version they started, and paid fees stay
* Portals past checkout, expired or completed portals, test links and finished check-ins don't change

Switching off or deleting a rule can complete check-in for guests who only had that step left. That starts **Portal check-in completed** workflows.

## Priced steps need Stripe

Once the workspace has an **Active** template or stay portals, these steps need a Stripe account with charges enabled: security deposits, required fees and priced damage waivers. Without one, creating, switching on or saving them shows **Connect Stripe and finish onboarding before using paid portal content.** See [Payments](https://docs.conduit.ai/portals/payments.md#connect-stripe).


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