> For the complete documentation index, see [llms.txt](https://user-help.runmags.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user-help.runmags.com/advertising-sales/extracurricular/non-english-agreements-and-invoices.md).

# Non-English agreements and invoices

A user with Sales access can specify that clients facing documents like agreements and invoices should be generated in the clients own language, rather than English.

Note: Besides English, RunMags currently supports German and Swedish as the two other languages that agreements and invoices can be presented in. If you have the need for another language and have the capability to help us with a translation, we'll be more than happy to accommodate that. Just contact us and we'll make it happen!

To change the language for a client, click the upper Edit button to change the overall account information. On the lower left, click the dropdown field and select the language for that specific client. Click the green Save button. From then on, all agreements and invoices for that client will be in the language specified.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://user-help.runmags.com/advertising-sales/extracurricular/non-english-agreements-and-invoices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
