> 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/projects/import-export/xlsform/settings-sheet.md).

# Settings Sheet

The settings sheet contains metadata about your form. In your case, only two fields are supported:

#### form\_title

This is the name of your form as it will appear to users. It’s typically shown at the top of the screen or on the form loading screen.

Example:

| form\_title              |
| ------------------------ |
| Customer Feedback Survey |

#### default\_language (optional)

This sets the default language that the form will use if no language is selected or if the device does not support language selection.

The value must match one of the language codes used in your label columns (for example, `en`, `fr-FR`, `es`, etc.).

Example:

| default\_language |
| ----------------- |
| en                |

You can include both fields in the same row:

| form\_title              | default\_language |
| ------------------------ | ----------------- |
| Customer Feedback Survey | en                |


---

# 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/projects/import-export/xlsform/settings-sheet.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.