---
title: Prerequisites for AIRA translations and setup
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Prerequisites for AIRA translations

A little preparation goes a long way toward smooth translation results. Before you start using AIRA, check that your project is ready.

1. **Languages** – Make sure that all your desired target languages are added in the _Languages_ application.\
   This step defines the [language variants](https://docs.kentico.com/modules/work-with-multilingual/multilingual-variant-of-content.md) that AIRA can create for your website. See the documentation on [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) for detailed setup info.

2. **Access rights** – Check that your [user role](https://docs.kentico.com/guides/digital-marketing/xperience-essentials/user-management-essentials-introduction.md) can access both **AIRA configuration** and **Content hub**. If you can’t see those apps, ask your Xperience administrator to grant you access to those spaces.

3. **Tone of voice (optional)** – To help AIRA reflect your brand’s personality, define your tone of voice in **Configuration** → **AIRA** application → **Content generation** tab.\
   For example: _Friendly and clear, with a touch of humor._

   > **Info:** The _Tone of voice_ field is limited to 256 characters, so you may want to take a bit of time to brainstorm a ToV prompt that is both brief and descriptive.

By preparing these basics, you’ll ensure your translations are as accurate as possible, and aligned with your brand identity from day one.

## Setting up automated translations in AIRA

Once your environment is ready, it’s time to **configure AIRA** for your first translations. This setup defines _how_ AIRA interprets and translates your content and ensures the results sound like your brand.

> **Tip:** Like most AI tools, AIRA delivers the best results when you refine your prompts over time. Start with an initial version, review the results, and adjust your prompts based on what you learn. Even slight changes to the translation prompt can make a significant difference.
>
> Set aside some time to fine-tune your translation process and prompts. This will help AIRA better match your brand’s tone and produce more natural translations.

### Open the AIRA configuration

Start by going to **Configuration** → **AIRA**.
Here you’ll find two key areas: one for _tone of voice_ (how your brand speaks) and one for _translation settings_ (how your text gets converted across languages).

Switch to the **Content generation** tab to review or define your tone of voice. It's located here and not in the translation settings because AIRA will use the definition you provide in this tab for both content generation and translation purposes. This way you make sure that your messaging is consistent across all markets from the very beginning.

### Define tone of voice

Your tone of voice is what gives your brand character. Even automated translations should sound recognizably **you**.

1. Add a short description that captures your messaging style.
   Example: _Professional yet approachable. Clear, concise, and empathetic._
2. **Save** your settings.

### Configure translation options

Now it’s time to teach AIRA how to handle your translations.

1. Go to the **Translations** tab.
2. Choose which data types can be translated:
   - _Text_
   - _Long text_
   - _Rich text (HTML)_

> **Info:** **For admins:** The available types depend on what your developers have enabled.

3. Create your **translation instruction (prompt)** – this is the most important specification that tells AIRA exactly what to do.\
   Think of it as your brand’s “translation brief”. You can mention tone, terminology, words to leave untranslated, or audience details.

> **Info:** Example:\
> _Translate the text accurately but naturally for local audiences. Keep the tone light and friendly, but still professional. Do not use emoticons. Keep brand names and slogans in the source language._

4. Keep the _Use tone of voice guidelines for translations_ option selected if you wish AIRA to use the tone of voice you defined earlier.
5. **Save** your prompt and settings.
6. Perform a few **test translations** to see how your setup behaves and adjust it as needed.

![AIRA translations configurated](https://docs.kentico.com/docsassets/modules/aira-translations-prerequisites-and-setup/aira-translations-configuration.png "AIRA translations configurated")

You’ve now built the foundation that tells AIRA _how_ to translate in a way that fits your brand voice. Although you can not adjust the **system prompt** that powers AIRA translation feature itself, you can still customize it to add your own flavor.