To ensure the proper functioning of the Guest Registration module, both for automatic submission to SES and the generation of traveler forms, it's essential to correctly capture the following data for each guest, even if the check-in is completed outside of Civitfun.
๐ Table of Contents
- Mandatory fields to capture
- Where to configure these fields
- Structure of the fields table
- Special behaviors of certain fields
- Final recommendations
- Frequently Asked Questions
๐งพ Mandatory fields to capture
- Document type
- Document number
- Document support number
- Nationality
- First name
- Last name
- Second last name
- Date of birth
- Gender (M/F)
- Email (either email or phone)
- Phone (either email or phone)
- Residence postal code
- Residence address
- Residence city
- Residence country
- Family relationship
โ๏ธ Where to configure these fields
If the check-in is done through Civitfun. Go to the Forms section from the Civitfun dashboard under the Configuration menu with an Admin user.
Configure each field using the Visible and Required columns.
- Checking Visible means the field will appear in the form but wonโt be mandatory.
- Checking Required will enforce that the field must be completed to finish the check-in.
ANNEX: Dynamic Forms
Dynamic forms allow you to configure different types of forms depending on the type of guest โ domestic or international, adults or children.
In this case, the fields need to be enabled for each guest profile individually, rather than applying them generically to all guests.
๐๏ธ Structure of the fields table
- Column 1: Display name in the check-in form.
- Column 2: PMS Mapping (or PMS availability status).
๐ What do the PMS availability statuses mean?
๐ด Not available in PMS
- The field can be collected in Civitfun but cannot be sent to the PMS.
- The data will only be stored in the Civitfun dashboard.
๐ Requires mapping
- The field does not exist in your PMS, but you can create and map a custom field in the PMS to receive data from Civitfun.
- If mapping exists, follow the instructions provided in each fieldโs detail.
Example:
โน๏ธ Special behaviors of certain fields
- Document support number: Required only if the document is a DNI or Residence Permit.
- Family relationship: Required only if the reservation holder is traveling with minors.
โ Final recommendations
- Review these fields across all configured languages in your dashboard.
- Ensure fields are properly marked as visible and required where needed.
- Coordinate with your PMS if youโre unsure about field availability or mapping options.
โ Frequently Asked Questions
What happens if a mandatory field is not completed by the guest?
The check-in process cannot be finalized until the field is completed.
Can I make fields visible without making them mandatory?
Yes. You can check only the Visible column and the field will appear as optional.
What does it mean if a field is locked?
These are system-critical fields tied to PMS integration. Contact support to modify them.
Can I activate fields even if they are not available in my PMS?
Yes, but the data will only be saved in the Civitfun dashboard and not sent to your PMS.
What happens if I donโt configure these fields?
You wonโt be able to generate traveler reports or send data to SES correctly.
If you have any questions about applying these settings, feel free to contact our support team or check related help center articles about validation and Guest Registration setup.
We hope this article was helpful! If you need further assistance, reach out to support@customer.civitfun.com โ we're happy to help. ๐โ๏ธ