> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/0-struktura-i-nawigacja/sekcja-section/sekcja-dynamiczne-tytuly-sekcji.md).

# Section - dynamic section titles

For components *A section* and *Checkbox group* It is possible to define dynamic section titles.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FYdYdVfoUvo0vkMB7qCDa%2FZrzut%20ekranu%20z%202020-07-07%2016-19-14(1).png?alt=media&amp;token=be0f2bf4-f000-4111-9823-5201a18239f9" alt=""><figcaption><p><em><strong>Figure 1.</strong> Appearance of the property allowing access to the dynamic section titles window</em></p></figcaption></figure>

## Adding a new dynamic title <a href="#dodawanie-nowego-dynamicznego-tytulu" id="dodawanie-nowego-dynamicznego-tytulu"></a>

After selecting the property (section *Other*) a window (drawer) opens that allows managing dynamic section titles.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2F2KjME915cfBfLBbrbrzc%2FZrzut%20ekranu%20z%202020-07-07%2016-19-47.png?alt=media&amp;token=254d422b-6908-43a4-b481-96ea28aaec8d" alt="" width="563"><figcaption><p align="center"><em><strong>Figure 2.</strong> Appearance of the window drawer without added dynamic section titles</em></p></figcaption></figure>

Clicking the **Add dynamic section title** causes a row to be added to the drawer — it represents a new title to be configured. If the component has no dynamic section title added, the contents of the drawer look as follows:

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FVyDy5LlWiyPOTDCTyvtF%2FZrzut%20ekranu%20z%202020-07-07%2016-20-35.png?alt=media&amp;token=00660a59-4240-4af2-b521-755c25618fd1" alt=""><figcaption><p align="center"><em><strong>Figure 3.</strong> Appearance of a newly added and unconfigured dynamic section title</em></p></figcaption></figure>

## Dynamic title configuration

In the view of the newly added row, the following properties can be defined:

* **Title key** — key from the tab **Translations**; after entering an existing key in the column **Preview** the corresponding value will be filled in.
* **Condition** — condition for the title to appear.
* **Style name** — the name of the style to apply to the contextual help.

## Order and sorting

Multiple elements can be added in the drawer of the dynamic section titles window. They are considered in order from top to bottom. Each row has a handle on the left side (6 dots), which allows you to grab the row and move it to the desired position to set the order of the list.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/0-struktura-i-nawigacja/sekcja-section/sekcja-dynamiczne-tytuly-sekcji.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
