> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.anghello.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Conditional Rules and Layout Fields

**Who is this for?** Site managers and administrators who configure the custom fields of the check-in kiosk.
**Prerequisites:** knowing how to [add a custom field](https://help.anghello.com/en/article/add-custom-fields-1sm7vxm/). The features described here are part of the **Advanced Fields** module: if they appear grayed out with a padlock, contact your Anghello representative to enable it.

Your custom fields aren't just for *collecting* information. You can also:

* **structure** the check-in form with pages and notice blocks,
* **make it smart** with conditional rules: show a field only when it's useful, or prevent a visitor from continuing until a condition is met.

This guide covers both features.

---

## 1. Structure the form: layout fields

These fields **expect no answer** from the visitor: they are only used to organize and lay out the check-in flow. You'll find them in the `Add Field` window, under the **Advanced Fields** section.


![](https://storage.crisp.chat/users/helpdesk/website/-/2/0/a/6/20a671ba57d61a00/scr-20260711-kmsd_1a53v2o.png =499xauto)


Since they don't collect any data, the usual options (`Enabled`, `Required`, `Anonymize Field`) are not displayed for them.

### The Notice Block

A **Notice Block** displays a message to the visitor: a safety rule, welcome information, an obligation to comply with. The visitor reads it but has nothing to enter.
**It is useful for delivering contextual information.**

**To add it:**

1. Click `Add Field`, then choose **Notice Block** in the Advanced Fields.
2. Fill in the options:

| Option | Purpose |
| ---- |
| **Title** | The block header (e.g. *Safety instructions*). |
| **Body** | The message displayed to the visitor (e.g. *Hard hats are mandatory across the entire site.*). |
| **Pictograms (optional)** | A pictogram illustrating the notice. Click `Pick a picto`. |
| **Style** | The background color, which sets the tone of the message. |

The available styles help you visually rank your messages: `None`, `Neutral`, `Risk`, `Obligation`, `Prohibition`, `Safety`, `Fire`.

> 💡 **Tip:** choose the style based on intent. An `Obligation` background for "hard hat required", a `Prohibition` background for "no photos": visitors understand the nature of the message at a glance, even before reading it.

### The Page Break

A **Page Break** splits the check-in form into **several successive pages**. On the kiosk, the visitor moves from page to page with the `Back` and `Continue` buttons.

It is useful when your check-in flow includes many fields: instead of one long, intimidating list, you offer a series of short, digestible steps.

**To add it:**

1. Click `Add Field`, then choose **Page Break**.
2. Fill in the **Next page title** field: this text is displayed at the top of the page that follows the break (e.g. *Your safety information*). Leave it empty to display no title.

All fields placed **after** a page break appear on the new page. Add as many breaks as needed to create as many pages as you want.

> 💡 **Tip:** group your fields by topic and separate each topic with a page break (*Identity* → *Purpose of visit* → *Safety instructions*). The check-in journey becomes much smoother.

---

## 2. Make the form smart: conditional rules

A **conditional rule** always follows the same logic: **If** the visitor gives a specific answer, **Then** something happens.

A concrete example we will follow throughout this guide:

> *If the visitor answers "Yes" to "Are you working in a hot work area?", then show the "Hot work permit number" field.*

The "Hot work permit number" field stays **hidden** for all other visitors: it only appears for those who need it.


![](https://storage.crisp.chat/users/helpdesk/website/-/2/0/a/6/20a671ba57d61a00/scr-20260711-knvh_qpvgf1.png =546xauto)


### The two possible effects

When the condition is met, the rule triggers one of these two effects:

| Effect | What it does | Target field? |
| ---- |
| **Show a field** | Reveals a field that was hidden by default. | Yes - you choose the field to reveal. |
| **Prevent continuing** | Blocks the visitor: the `Continue` button (or the check-in validation) is disabled as long as the condition remains true. | No - it blocks the whole flow. |

**"Show a field"** is used to ask relevant follow-up questions without weighing down the form for everyone.

**"Prevent continuing"** is used to enforce an access condition. Example: *If the visitor answers "No" to "Do you have a hard hat?", then prevent continuing.*

> **Important:** a field to reveal must exist **before** you create the rule. First create "Hot work permit number" (it will stay hidden), then create the rule that shows it.

### Where to create a rule

You have two entry points, which act on the same rules:

* **From a field**: open a field, then the **Rules** tab. The open field is automatically suggested as the trigger. Handy when starting from a specific question.
* **From the site**: in the site settings, the **Conditional rules** section gives an overview of all your rules, on check-in and check-out. Handy to review or reorganize everything.

### Create a rule, step by step

1. Click `Add a rule`. The **New rule** window opens, organized in two parts: **If** … **Then** …

2. **If the field**: choose the trigger field.

> **Important:** only **choice fields** can trigger a rule, i.e. **Yes/No** fields and **dropdown lists**. A free-text or numeric field cannot be a trigger, because its answers are not predictable.
>
> If no choice field exists yet, the window invites you to create one first.

3. **has one of these answers**: select the answer(s) that trigger the rule. For a dropdown list, you can check several values; for a Yes/No field, choose `Yes` or `No`.

4. **Then**: choose the effect:
* **Show a field**: an additional menu appears to choose the **field to show**.
* **Prevent continuing**: no additional setting, the effect blocks the flow.

5. Click `Save rule`.

Your rule is immediately active on the kiosk.

### Read the warnings carefully

Anghello flags configurations that need attention. Most are simple **warnings** (the rule can still be saved), except the duplicate, which **blocks** saving:

| Message | Meaning |
| ---- |
| **This rule already exists** | An identical rule (same answers, same effect) already exists. Saving is blocked: adjust it or cancel. |
| Field order | The trigger field comes *after* the field it is supposed to show. Move the trigger higher in the form so the rule makes sense. |
| Circular dependency | Two rules call each other (A shows B which shows A). Simplify the chain. |
| Disabled field | The trigger or the target is disabled: the rule will not apply until it is re-enabled. |

---

## Combine both: a complete example

You can make a **Notice Block** the target of a **Show a field** rule. The message then only appears in the relevant case:

> *If the visitor answers "Delivery" to "Purpose of the visit?", then show the Notice Block "Go to unloading dock B".*

Result: only delivery drivers see this notice; other visitors aren't cluttered with a message that doesn't concern them.

> **Note:** a **Page Break** cannot be the target of a rule. Page breaks structure the form permanently; fields and notice blocks are what display conditionally.

---

## In a nutshell

* **Notice Block**: display a message (title, body, pictogram, color style): the visitor reads it without entering anything.
* **Page Break**: split the check-in form into several shorter pages.
* **Conditional rule**: **If** a choice field receives a specific answer, **Then** *show a field* (ask the right question to the right person) or *prevent continuing* (enforce an access condition).

> 💡 **Final tip:** always test your configuration by running a test check-in on the kiosk. Answer "Yes" then "No" to your trigger questions to check that the right fields appear and disappear as expected.