> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/questions/question-types/standard/text-comment-field.md).

# Text / Comment Field

The text / comment field question is based on the [entry field](/form-management/form-designer/answers/answer-types/entry-field.md) answer type.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBhEHQX1dJgLFMgYGxh%2F-MBhF7Hjbg4PpfqKEiUE%2Fimage.png?alt=media\&token=7461c3ae-0cec-4ddc-a0db-bec1db8adcfd)

You may also have larger fields using the **Comment field** question.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBhEHQX1dJgLFMgYGxh%2F-MBhFAyrt9Zs84tYWV1Z%2Fimage.png?alt=media\&token=4b116bdd-ddba-4d83-ab51-f5a9abccd628)

{% hint style="info" %}
You may check the [fields properties](/form-management/form-designer/answers/answer-properties/field-properties.md) page for a detailed overview of the different fields capabilities (validation, layouts ..) 
{% endhint %}

## 🏷️ Label Positioning

Labels of the fields can be positioned in 2 different ways

Either inside the field

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBhKdDjGLtVEBNrBEKr%2F-MBhL2Zvo3z0RzHsX84z%2Fimage.png?alt=media\&token=2c734f0e-695d-43ad-8425-636069b6e02d)

Or outside the field 

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBhKdDjGLtVEBNrBEKr%2F-MBhLcWEnyeae-8F1gFL%2Fimage.png?alt=media\&token=27f6485f-d211-4631-ae9e-2f97b924e9c3)

You may switch from one or the other positioning using the **fields label position** property of your [survey properties](/form-management/form-designer/form-settings.md).

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBhKdDjGLtVEBNrBEKr%2F-MBhLKwfuvCKfTgO-T2Y%2Fimage.png?alt=media\&token=180080a3-58d1-45fa-8b77-50da60e81d08)

{% hint style="info" %}
Label positioning is set globally for all the fields of your survey.
{% endhint %}


---

# 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.ngsurvey.com/form-management/form-designer/questions/question-types/standard/text-comment-field.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.