# Sections

The **Sections** feature in Activity Templates is a visual grouping tool that helps organize activity items and enforce specific requirements for operators. Sections allow you to group related items together, making the activity template more structured and user-friendly. Each section can be marked as either **required** or **optional**, which determines the level of enforcement for completing the fields within that section.

#### Overview

To define a section in an activity template, you will see two separate elements: one for the **Start Section** and one for the **End Section**. These elements must be placed outside the intended activity items for the section.

<figure><img src="/files/Z99nBamWPqW8on4IrBaj" alt=""><figcaption></figcaption></figure>

**Example Structure:**

* **Start Section**: Denotes the beginning of the section and its properties.
* **End Section**: Denotes the end of the section.

The sections will visually group the activity items and control how they behave based on whether they are required or optional.

### Section Types: Required and Optional

Sections can be classified as **Required** or **Optional**. The difference between these types impacts how users interact with the fields in the section.

#### Section Behavior Table

| **Section’s Behavior** | **Required Field**                                   | **Optional Field** |
| ---------------------- | ---------------------------------------------------- | ------------------ |
| **Required Section**   | Must be filled                                       | Optional to fill   |
| **Optional Section**   | Must be filled if at least one other field is filled | Optional to fill   |

<figure><img src="/files/pCGMM9xoqQl9lxRq4syY" alt=""><figcaption></figcaption></figure>

#### Notes for Existing Template Migration

* All existing activity template sections that are marked with **SECTION** will automatically have `required = true` to maintain the behavior from previous versions.
* If you want to modify the behavior of existing sections, you need to explicitly adjust the section settings to change their required or optional status.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/activity-templates/activity/elements/data-types/sections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.