> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/guest/configuration/guest-sites/manage-multiple-languages-for-guest.md).

# Manage Multiple Languages for Guest

Learn how to manage multiple languages for your Verkada Guest

On the start screen of the [Verkada Guest](https://docs.verkada.com/docs/verkada-guest-overview.pdf) app, visitors will see an option to change the language.

{% hint style="danger" %}
At least one Guest Type must be full translated into a language other than the site-default language for the language option to appear. 
{% endhint %}

***

## Enable multiple languages

{% hint style="info" %}
Currently, you can enable English, French, Spanish, Portuguese, German, Italian, Mandarin (Chinese Simplified), Korean, Japanese, Dutch, Finnish, Russian, Danish, and Somali.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Guest.**
{% endstep %}

{% step %}
**On the left navigation, click Guest Settings.**

a. At the top, select **Sites**.\
b. Use the dropdown to select the site that you want the supported languages on.\
c. On the left side, select **Guest Languages**.\
d. Select the languages you want to enable for Guest. Double-click a language to set it as the default.
{% endstep %}
{% endstepper %}

***

## Translate Guest types

If you have already configured Guest types, they should have an exclamation (**!**) icon next to them.

The names of your Guest types need to be translated to the respective language(s).

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Guest.**
{% endstep %}

{% step %}
**On the left navigation, click Guest Settings.**
{% endstep %}

{% step %}
**Under Organization, select Guest Types.**
{% endstep %}

{% step %}
**Click Manage Guest Types.**
{% endstep %}

{% step %}
**Select the Guest type to add translations to your Guest type. Click the dropdown to insert your translation.**
{% endstep %}

{% step %}
**Add the translation and click Save.**
{% endstep %}
{% endstepper %}

***

## Translate documents

Once you [create your document](/guest/getting-started/get-started-with-verkada-guest.md), you can add a translation to it.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Guest.**
{% endstep %}

{% step %}
**On the left navigation, click Guest Settings.**
{% endstep %}

{% step %}
**At the top, click Sites > Guest Languages.**
{% endstep %}

{% step %}
**Select the language you want to translate. Double-click the language you want to be the default.**
{% endstep %}

{% step %}
**Under Guest Settings > Organization, scroll down to Documents > Manage Documents.**

{% hint style="info" %}
If you see an exclamation mark next to a document for a site, the document has not been translated yet.
{% endhint %}
{% endstep %}

{% step %}
**On Documents:**

1. Scroll to a document for your site that you want to translate.
2. At the top right, click the language dropdown and select the language you want to use for the translation. The default language is shown at the top.
3. (Optional) At the top left, change the document’s name.
4. Translate the document’s name and content.
5. At the top right, click the checkmark icon to save your changes, then close the document.
   {% endstep %}
   {% endstepper %}

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=NWVEuGCvY9o).
{% endhint %}


---

# 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.verkada.com/guest/configuration/guest-sites/manage-multiple-languages-for-guest.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.