The customer data form builder

Customer Data is where you decide what Gurita asks about every guest — the sections of the customer profile, the questions on the online guest form, and the order they appear in. This page describes the redesigned builder: a single workbench with the section list on the left, the fields of the selected section in the middle, and everything about the selected item on the right. Managers and administrators use it; front-desk staff never see it.

Note: The redesigned builder is optional. Until it is switched on (see Turning it on), /customerdatagroup opens the previous editor, which works the same way but arranges everything in nested dialogs. Guests see no difference either way — the builder only changes how you edit.

Who can access this: requires the Customers update permission. It sits under Master Data → Customer → Customer Data.

Turning it on

1. Go to Settings → Plugins.
2. On the Gurita Beta card, switch on Use redesigned data form builder.
3. Reopen Customer Data.

You can switch back at any time — the two editors read and write exactly the same sections and fields, so nothing is converted and nothing is lost by changing your mind.

The form builder

How the screen is laid out

Area	What it holds
Left — sections & groups	Every section, in the order guests see them. A search box above it finds sections and fields, so you can answer "where is that passport question defined?" without opening each one.
Middle — fields	The fields of the selected section, with their number, type, width and actions.
Right — inspector	Everything about whatever you last clicked: a field, or the section itself. It follows your selection.
Top bar	A validity indicator, Export, and Save. Save shows how many sections you have changed.

Nothing you edit is written until you press Save — you can rename, reorder, add and delete freely, check the result in Preview, and only then commit, or navigate away and discard everything.

Note: Installing a starter pack is the one exception: it creates its section on the spot, so navigating away does not undo it.

Working with sections

Click a section in the left list to select it. The inspector then shows three tabs: Settings, Dependencies and Title & copy.

Settings

Setting	What it does
Key	The section's storage name. Shown but not editable — every answer ever saved is filed under it, so it is fixed after the first save.
Connect to previous group	Renders this section joined to the one above instead of starting a new card. Use it when one question should reveal several sections at once.
Can be activated/deactivated by customer	Adds a "does this apply to me?" tick before the section's fields appear — for example dive insurance. You then write the question itself per language.
At least one connected group must be activated	With several optional sections, forces the guest to turn on at least one.
Guest form / Master data	Whether the section appears on the online guest form, on the internal customer profile, or both.
Asset / Customer type	Limits the section to particular properties, or to Divers / Snorkelers / Guests only. Leave both empty for everyone, everywhere.
Trim value, Upper case, Lower case	Clean-up applied to every field in the section.

Group actions

Copy duplicates the section, Export JSON downloads its definition, and Delete removes it.

Warning: Deleting a section takes every field definition in it with it. Gurita asks you to confirm and names what will go. Answers already stored under those fields stay in the database but are no longer shown anywhere, and the section cannot be brought back from this screen. A section marked Locked cannot be deleted at all.

Title & copy

One block per guest-form language, each with the section's name and optional intro and closing text. The intro and closing are formatted text: the pane shows a preview, and clicking it opens the full editor — headings, lists, links, images and tables — in a window. Changes there are kept only when you press Save in that window. A language with no name yet is marked missing, and the tab shows a dot so you can see at a glance that something is untranslated.

Working with fields

Adding a field

Hover between two rows and a small Insert here strip appears — click it to add a field exactly there rather than at the end. Add field at the top right of the field list appends one instead. Either opens the type palette, grouped into Text, Choice, Date & time, Upload, Consent and Presentation.

Note: Some types can only be drawn by the redesigned guest form. If your property still uses the classic guest form, the palette marks those types with a warning — a guest would simply see nothing where the field should be.

The field key

New fields get a generated key which you can rename until the field is saved for the first time. Keys allow letters, numbers and underscores, and must start with a letter; anything else is refused as you type, and so is a key another field in the same section already uses. After the first save the key is locked and shown with a padlock, because every stored answer is filed under it.

Field settings

Setting	What it does
Type	What the field asks for. It stays changeable after saving, but the inspector warns which conversions are safe and which need the stored answers rewritten — read that note before changing it on a field guests have already filled in.
Width	How much of the 12-column row the field occupies.
Guest form / Master data / Hide for customers and agents	Where the field appears, and whether it is staff-only.
Semantic role	See Semantic roles.
Where it is offered	Restricts the field to particular assets or customer types, like the section-level setting.
Synchronize	For connected systems: sends this field's answer to the named target field.
Icon	An optional symbol shown beside the field, picked from a searchable list grouped by what the symbol depicts.
Required, Trim value, Upper case, Lower case	Whether an answer is mandatory, and how the text is cleaned up.
Minimum / Maximum / Default value	Limits and a pre-filled value, where the type supports them.

Choice fields get an option editor; yes/no fields get their own Yes/No wording per language; consent and waiver fields get the document or page the guest must open before ticking. An HTML field has no label of its own — under Title & copy it offers the same formatted-text editor as a section's intro, and whatever you write there is the block the form displays.

Reordering, copying and deleting

Drag a row to move it, or focus it and hold Alt with the up/down arrow keys. The copy icon duplicates a field within the same section; the bin removes it. Fields marked with a padlock are locked by your configuration and cannot be deleted.

Rules: showing a field only sometimes

Open a field (or a section) and switch to Dependencies to say when it should appear. Press Add condition and build the rule from three parts:

1. The field it depends on — chosen from a searchable list grouped by section.
2. The comparison — the options offered depend on what kind of field you picked. A yes/no field offers is yes / is no; a date offers is before / is on or after; a section offers is activated.
3. A value, where the comparison needs one.

Add more conditions and switch the joining word between and and or by clicking it. Above the rows, Gurita writes the finished rule back to you as a sentence, so you can read what the guest will experience instead of decoding a query.

A rule on a section hides the whole card. A rule on a field hides just that field. Stored answers are never deleted by a rule — a hidden field simply stops being asked and stops counting towards the form's completion.

Tip: Point a rule at a staff-only field and Gurita warns you: guests never answer that field, so the rule could never unlock for them.

Depends on this field underneath lists everything that points at the field you are looking at — check it before changing a field's type or deleting it.

Semantic roles

A role tells Gurita what a field means, independent of what you called it. Tag a field as Passport number and features that need a passport number will find it, whatever key or label your property uses — the passport-scan auto-fill and the dive-certification lists both work this way.

Roles are optional, and each one can be claimed by only one field per property. If two fields claim the same role, both are flagged and saving is blocked until you resolve it. Suggest proposes a role based on the field's key.

Preview

Preview in the section header replaces the field list with the section as a guest or a staff member will actually see it. Switch between the Guest and Staff audiences and between your guest-form languages — the preview uses the language you pick, not the language of the admin screen — then use Back to fields to return. Nothing typed into a preview is stored.

Checking and saving

The indicator in the top bar is always visible and has three states:

Indicator	Meaning
Definition valid (green)	Nothing to fix.
n warnings (amber)	Worth looking at, but you can still save — for example a rule pointing at a field that no longer exists, or a missing translation.
Save blocked (red)	Something must be fixed first, such as two fields sharing a key, a dropdown with no options, or two fields claiming one role.

Click the indicator to list every issue; click an issue to jump straight to the field it concerns.

Save writes only the sections you actually changed, and asks you to confirm first. The confirmation shows how many customers already hold an answer for the field you were last editing — a green zero means the change destroys nothing.

Note: Rules written in the previous format are converted for you automatically, and editing here cannot lose one. A banner appears only for the few Gurita could not read — those rules are not in force at all, so open each field it names and build the condition again under Dependencies.

Starting from scratch

On a property with no sections yet — or from Starter packs in the bottom-left corner — Gurita offers ready-made sections you can install and then adapt: emergency contact, diet and allergies, insurance, dive certification, flight details, and a medical declaration. Each arrives with sensible fields and English and German labels; the emergency-contact, insurance, dive-certification and flight packs also come with semantic roles already assigned. They deliberately do not overlap the sections every property starts with (personal data, address, contact, passport), so installing all of them is safe.

Keyboard use

The builder can be operated without a mouse: Tab moves between sections, field rows and controls, Enter or Space selects a field row, and Alt with the up/down arrows moves the focused field.

Related chapters

• Customers — the profile these sections build, and where the answers are read and edited.
• Guest forms — the online form your guests fill in, assembled from these sections.
• Forms and Surveys — standalone questionnaires, which are configured separately.
• Dive — dive certification fields and how roles let the dive module find them.
• Settings & Administration — the Plugins page, where the redesigned builder is switched on.