> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/user-settings/language.md). # Language ### Overview Language settings control UI labels and system text. They do not translate content entered by Teammates. ### Key Concepts * **UI language**: language for navigation, labels, and system messages * **Locale formatting**: date and number formats tied to language or region (when enabled) ### How It’s Used Use language settings during onboarding. Revisit language settings when delivery teams span multiple regions. ### Benefits * Clearer UI labels across regions * Reduced misinterpretation of system messages and date formats ### Setup Steps Use the full setup guide: * [Language Preferences](/getting-started/language-preferences.md) ### Best Practices * Standardize date interpretation for planning and reporting. * Standardize deliverable language per Project when needed. ### Summary Language settings control UI labels and locale formatting (when enabled). --- # 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://help.transform.ai/user-settings/language.md?ask=&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.