> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/system-settings/languages-and-translations.md).
# Languages & Translations
Choose the languages offered to customers and edit every text in the system.
## Languages
**System Settings → Languages** sets the **Available languages**, the languages customers can choose from. CodiCo Dispatch supports 14 languages: German, Greek, English, Spanish, Finnish, French, Italian, Dutch, Norwegian, Polish, Portuguese, Russian, Swedish and Turkish. Click **Save**.
## Translations
**System Settings → Translations** lists every text in the system with its translation in each language.
The Translation page.
* **Search by key** finds a text.
* The language selector chooses which language columns are shown.
* **Edit** changes the translations of a text.
* **Export to CSV** downloads all texts.
{% hint style="warning" %}
Some texts contain placeholders such as `:userName` or `:booking_id`. Keep them unchanged in every language; the system fills them in.
{% endhint %}
## Watch the video
{% embed url="" %}
Translations — Manage your System Texts
{% endembed %}
---
# 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://codico-dispatch.gitbook.io/documentation/system-settings/languages-and-translations.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.
