> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/administration/user-account-settings/user-language.md).

# User language

The language you select for your user account determines the language of the Hippoly interface.

{% hint style="info" %}
Note that not all content will necessarily appear in your preferred user account language. Each workspace also has its own [workspace language setting](/administration/workspace-administration/workspace-language.md), chosen by a workspace admin, which controls the language used for templates, emails, and other workspace-specific content.
{% endhint %}

## Change language for your user account

{% stepper %}
{% step %}
Go to <https://secure.hippoly.com/#/account-settings/settings> or navigate to your account settings by clicking your name at the top right corner of the screen. &#x20;
{% endstep %}

{% step %}
Expand the **Language** section.
{% endstep %}

{% step %}
Select your preffered language from the dropdown .
{% endstep %}

{% step %}
Click the `Save` button.
{% endstep %}
{% endstepper %}


---

# 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.hippoly.com/administration/user-account-settings/user-language.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.