> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-editor/built-in-elements/label.md).

# Label

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2Fx17wJlurXlAR48v8O1bz%2Fimage.png?alt=media&amp;token=916de653-1da3-4df0-b656-7ea0b638eb9d" alt="" width="66"><figcaption><p>Label Element</p></figcaption></figure></div>

The **`Label`** element is used as a label or title for the interactive elements like [Input](/app-editor/page-editor/built-in-elements/input.md), [Dropdown](/app-editor/page-editor/built-in-elements/dropdown.md), [Multi-line](/app-editor/page-editor/built-in-elements/multi-line.md), etc and it is part of composite interactive elements like [Checkbox](/app-editor/page-editor/built-in-elements/checkbox.md) and [Toggle Switch](/app-editor/page-editor/built-in-elements/toggle-switch.md). Additionally the Label element is also part of Data Field composite elements which are used in [Forms](/app-editor/page-editor/working-with-forms.md).

It behaves similar to [Inline Text](/app-editor/page-editor/editing-text.md#inline-text) element, and allows you to edit text. See [Editing Text](/app-editor/page-editor/editing-text.md) for more information.

***

## Options

The [Options tab](/app-editor/page-editor/page-element-settings.md#options-tab) settings for this element are described below:

### `Associated Input ID`

{% hint style="success" %}
The Associated Input ID is preset in several composite elements like [Checkbox](/app-editor/page-editor/built-in-elements/checkbox.md) and [Toggle Switch](/app-editor/page-editor/built-in-elements/toggle-switch.md), and Data Field composite elements used in [Forms](/app-editor/page-editor/working-with-forms.md).
{% endhint %}

This setting associates this label element with its associated input element like [Input](/app-editor/page-editor/built-in-elements/input.md), [Dropdown](/app-editor/page-editor/built-in-elements/dropdown.md), [Multi-line](/app-editor/page-editor/built-in-elements/multi-line.md), [Checkbox](/app-editor/page-editor/built-in-elements/checkbox.md), [Toggle Switch](/app-editor/page-editor/built-in-elements/toggle-switch.md), etc. You provide the [Element ID](/app-editor/page-editor/page-element-settings.md#advanced-tab) of the associated element here.


---

# 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.zingy.ai/app-editor/page-editor/built-in-elements/label.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.