> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/system/settings/languages.md).
# Languages
You can activate or deactivate available language, or create your own (**Content languages** feature) and use it as a channel for product information.
To do so click on a slider on the left side of a language bar.
{% hint style="info" %}
Please keep in mind that it's not enough to activate a new language, it must also be activated for all users who need to have access to it. A description of how this can be done is available [here](https://usermanual.ergonode.com/system/users/language-restrictions).
{% endhint %}
To create your own language, click on ***Add language*** above the list. Fill in ***Name***, ***Language***, ***Code*** and ***Workflow***, and optionally choose an ***Icon*** (a brand logo, for example for a marketplace channel). The code must be unique and cannot be edited later. To find a language in the list, use the magnifying glass icon.
It's mandatory to link language to [workflow](https://usermanual.ergonode.com/workflow/information). You can use a different workflow for every activated language; the badge next to an active language shows its workflow. To change it, click on the ***edit (pen)*** icon. The ***Edit language*** window also lets you change the language's ***Name***, ***Language*** and ***Icon***; its ***Code*** cannot be changed.
Assign a workflow by choosing one from the list.
Click on ***Save changes***.
---
# 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://usermanual.ergonode.com/system/settings/languages.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.
