Skip to main content

Identity Check

The Identity check overview page in the Operations Platform helps your team confirm that a guest is who they say they are. It is the review queue for the identity and travel-document data guests submit during online check-in.

This article is written for the front-desk staff and managers who work this queue day to day, and for the administrators who need to understand where the data comes from. Guest-facing capture (uploading a passport, signing a registration form) is described here only as how the operator reviews what the guest submitted.

1. Who Can Use This​

Identity Check is a host-facing operational capability. On Apaleo properties it has its own page, which you reach from the Operations Platform sidebar as Identity check overview. On Mews and Opera Cloud properties there is no such page, and you confirm IDs from the reservation instead (section 4).

In short, your property needs to run on Apaleo, and your Staff User Account needs the Host role. Section 4 explains why the page can be missing, and how to confirm a guest's ID when the page is not there at all.

2. Identity Check (the Verification Queue)​

The Identity check overview page is a review queue for the identity and travel-document data guests submit during the online check-in Legal step: for example passport or ID scans, the machine-readable-zone (MRZ) data read from a document, and the guest's signature on the registration form.

From the queue, staff review each submission and confirm that the captured document and details are in order. This is the operator-side counterpart to the guest's check-in upload. The guest submits, your team verifies.

info

Which legal fields and documents a guest is asked for, and therefore what lands in this queue, is controlled by the registration-form configuration (Settings → Operations → Registration Form). See Download the Registration Form (Meldeschein) for the form itself. Adjusting the captured fields is an administrator task.

3. Where the Data Comes From​

Identity Check shows what the guest submitted during the check-in Legal step: the document scan, the MRZ read and the signature. That capture happens in the guest journey and is surfaced to your team as a queue to review.

4. Availability​

Whether the page is there for you depends on the property's PMS and on your role:

  1. Your PMS. The Identity check overview page exists only for properties running on Apaleo. On Mews and Opera Cloud properties there is no such entry in the sidebar at all. See the note below for what to do instead.
  2. Your role. The page requires the Host role. A staff member without it will not see it.

The page is not tied to a pricing tier and is never shown locked. See Pricing Tiers.

ℹ️ Note: These are separate conditions. The PMS decides whether the page exists at the property, and your role decides whether you see it there.

warning

No Identity check overview page does not mean no identity check. Only the standalone queue page is Apaleo-only. Confirming a guest's ID works on every supported PMS. On Mews and Opera Cloud you do it per reservation instead of from a queue:

The document scan, the MRZ read and the signature are captured in the guest journey on every PMS as well. See ID Scan & Verification. What a non-Apaleo property lacks is the cross-reservation worklist, not the capability.

5. Conclusion​

Identity Check confirms the documents and details guests submitted at check-in. The Identity check overview queue needs the Host role and exists only on Apaleo properties (section 4), while confirming an ID itself works on every PMS, per reservation. For the data guests submit, see Download the Registration Form (Meldeschein); for the guest-side upload and scan, see ID Scan & Verification.

Was this article helpful?