---
title: AIRA configuration
related:
  - https://docs.kentico.com/documentation/business-users/aira.md
  - https://docs.kentico.com/documentation/developers-and-admins/configuration/aira-configuration/agent-configuration.md
---

> 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).

AIRA is an AI-powered agent that can increase the productivity of content editors, marketers and copywriters by offering [in-product guidance](https://docs.kentico.com/documentation/business-users/aira.md#aira-in-product-guidance) and automating content-related tasks with the use of various AI-backed [features](https://docs.kentico.com/documentation/business-users/aira.md).

## Privacy and data protection

All data processed by AIRA is commercially protected.

Neither Kentico nor the underlying AI models store or log raw customer data inputs, prompts, or responses generated when using AIRA features. All data is discarded after each interaction with AIRA and is not used to train the underlying models. To learn more, see the privacy guarantees provided by Microsoft Azure for [Azure OpenAI model privacy](https://learn.microsoft.com/en-us/legal/cognitive-services/openai/data-privacy?tabs=azure-portal) and [Azure Image analysis privacy](https://learn.microsoft.com/en-us/legal/cognitive-services/computer-vision/imageanalysis-data-privacy-security).

## AIRA credit balance

To view your AIRA credit balance:

1. Open the **AIRA** application.
2. On the **Overview** tab, you can see the amount of credits you have available and information about the next credit renewal.

To increase your credit balance, select the _Get more credits_ button and fill out the request form.

> **Info:** To learn more about AIRA Pricing, see [AIRA Pricing, Usage, & Policies](https://www.kentico.com/platform/aira-pricing-usage-policies)

## Track AIRA usage

To review how credits are consumed across AIRA features:

1. Open the **AIRA** application.
2. Switch to the **Usage** tab to see detailed usage statistics. The page displays usage by source, including consumed credits and request counts.
   - Use **Search** to find specific sources.
   - Use **Filter** to view the usage since the last renewal.
   - Use **Refresh** to reload the latest data.

By default, the **Usage** tab shows data for the last 30 days.

> **Tip:** On the **Overview** tab, admins can use the **Export usage CSV** button to export usage data from the past 90 days.

## Manage AIRA features

Most [AIRA features](https://docs.kentico.com/documentation/business-users/aira.md) are active by default. You can disable specific AIRA features if your project requires it.

1. Open the **AIRA** application.
2. Switch to the **Feature settings** tab.
3. Deselect the AIRA features you don't want users to use in the project.
4. **Save** the settings.

![Feature settings of the AIRA application](https://docs.kentico.com/docsassets/documentation/aira-configuration/aira-app-feature-settings.png "Feature settings of the AIRA application")

> **Info:** The **Segment condition builder** AIRA feature is disabled by default and can be enabled if your project uses [customer data platform](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform.md). See [Segments for profiles](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/segments.md) for more information.

## AIRA file storage

Images uploaded by users to the [AIRA chatbot interface](https://docs.kentico.com/documentation/business-users/aira.md#aira-in-product-guidance) are stored in the **\~/assets/aira** project folder. These files persist for up to 48 hours, before being removed by the _AIRA conversation attachment cleaner_ [scheduled task](https://docs.kentico.com/documentation/developers-and-admins/customization/scheduled-tasks.md).

The AIRA module automatically registers this path in the [storage path registry](https://docs.kentico.com/documentation/developers-and-admins/api/files-api-and-cms-io/file-system-providers/storage-path-mapping.md), so it is included in automatic storage path mapping alongside other system paths.

## Disable AIRA globally

To globally disable all [AIRA features](https://docs.kentico.com/documentation/business-users/aira.md), including [in-product guidance](https://docs.kentico.com/documentation/business-users/aira.md#aira-in-product-guidance) in your project:

1. Open your Xperience project.
2. In the _appsettings.json_ file, add a new configuration key: `"CMSEnableAira": false`.
3. Save your project.

All AIRA features are now disabled in your project.

> **Note:** To enable AIRA globally again, change the value of `"CMSEnableAira"` to `"CMSEnableAira": true`.

## Adjust the tone of voice

You can adjust the behavior of [AIRA content generation](https://docs.kentico.com/documentation/business-users/aira.md#content-generation-and-refinements) and [AIRA translations](https://docs.kentico.com/documentation/business-users/aira.md#aira-translations) by specifying the tone of voice guidelines:

1. Open the **AIRA** application.
2. Switch to the **Content generation** tab.
3. Fill in the **Tone of voice guidelines**:
   - You can describe your organization's tone of voice guidelines (professional, simple, humorous, etc.). AIRA will use this tone when [generating content](https://docs.kentico.com/documentation/business-users/aira.md#content-generation-and-refinements) or when [translating content](https://docs.kentico.com/documentation/business-users/aira.md#aira-translations). If not specified, AIRA uses a neutral tone.
4. **Save** the settings.

The settings apply globally for all content types and fields with the relevant AIRA features enabled.

## Add AIRA features to your content types

Some [AIRA features](https://docs.kentico.com/documentation/business-users/aira.md) need to be manually enabled for individual fields of your [content types](https://docs.kentico.com/documentation/developers-and-admins/development/content-types.md):

1. Open the **Content types** application.
2. Select a content type or a [reusable field schema](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md).
3. On the **Fields** tab, select the [field](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor.md) for which you want to enable AIRA features. You can add AIRA features to fields:
   - With the **Text**, **Long text**, **Rich text (HTML)**, or **Taxonomy** data type.
   - Using the **Rich text editor**, **Text area**, **Text input**, or **Tag selector** form component.
4. Expand a field and scroll down to the **AIRA features** section.
5. Select **Add AIRA feature** and choose the feature you want to enable:
   - **Generate image description during mass upload** – generates an SEO-friendly description of an image based on its content during [mass upload](https://docs.kentico.com/documentation/business-users/content-hub/content-item-assets.md#mass-asset-upload).
   - **Automatically assign tags to images during mass upload** – automatically assigns tags from the defined [taxonomy group](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) based on the image content during [mass upload](https://docs.kentico.com/documentation/business-users/content-hub/content-item-assets.md#mass-asset-upload).
   - **Rich text editor refinements** – supported for text fields using the _Rich text editor_ form component. Allows editors to select text and refine it in place using predefined options (make text shorter, improve writing and grammar, etc.), or apply a custom prompt and send it to AIRA for refinement. Unlike content generation refinements, which replace all text in the field, rich text editor refinements allow you to select and refine specific sections of text.
   - **Generate content** – generates text content for the field based on the [context](https://docs.kentico.com/documentation/developers-and-admins/configuration/aira-configuration.md#configure-the-context-for-generation) from other fields and AIRA instructions. Also allows users to refine existing text. Available for fields with the _Text_, _Long text_, or _Rich text (HTML)_ data type. See [Configure AIRA content generation and refinements](#configure-aira-content-generation-and-refinements) for the full configuration.
     1. Select **Continue**.
     2. Provide **AIRA instructions** describing the purpose of the field and any guidance for content generation.
     3. Select **Save**.
6. **Save** the field editor.

The selected AIRA feature is now enabled for the given field.

![AIRA feature added to a content type field](https://docs.kentico.com/docsassets/documentation/aira-configuration/Field_editor_AIRA_features.png "AIRA feature added to a content type field")

Repeat the process for all fields and content types where you wish to enable the AIRA features.

> **Info:** **Use AIRA features outside of content types**
>
> AIRA features are not restricted to content types in the _Content types_ application. You can use the same process to enable AIRA features in other field editors, for example for the fields of a [custom object type](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md) in the _Modules_ application.
>
> However, note that [content generation](#configure-aira-content-generation-and-refinements) is not fully supported outside of the _Content types_ application.

## Configure AIRA translations

You can adjust the behavior of [AIRA translations](https://docs.kentico.com/documentation/business-users/aira.md#aira-translations), which is used for the [translation of content items](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#translate-content-items) and [translation of pages](https://docs.kentico.com/documentation/business-users/website-content/translate-pages.md). To configure AIRA translations:

1. Open the **AIRA** application.
2. Switch to the **Translations** tab.
3. Select the data types allowed for translations.
   - Allows you to choose the field [data types](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor/data-types.md) you want translated (e.g., _Long text_, _Text_, _Rich text (HTML)_, etc.).
4. Specify instructions for translations.
   - Allows you to add custom instructions for how your content should be translated by AIRA, for example, brand terminology, formatting rules, words to leave untranslated, etc.
   ![Configure AIRA translations](https://docs.kentico.com/docsassets/documentation/aira-configuration/configure-aira-translations.png "Configure AIRA translations")
5. Set whether to use tone-of-voice guidelines for translations.
6. **Save** your changes.

The AIRA translations are now configured.

### Configure translation of specific fields

All content type fields of the data types allowed for translations are automatically enabled for translation. To specify which content type fields you want to translate:

1. Open the **Content types** application.
2. Select a content type.
3. On the **Fields** tab, select which [fields](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor.md) you want to configure the translation for.
4. Expand a field and scroll down to the **AIRA features** section.
5. Select or clear the **Include field in translation** checkbox.
   - The checkbox is only available if the [data type](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor/data-types.md) of the field is [allowed to be translated](#configure-aira-translations).
6. **Save** your changes.

You have successfully configured translation for a specific field.

### Configure translation of Page Builder component properties

You can specify which properties of [Page Builder components](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md#page-builder-components) (widget, section, etc.) you want to exclude from translation using the `ExcludeFromAiraTranslation` attribute.

```csharp title="Example"
using Kentico.Xperience.Admin.Base;
using Kentico.PageBuilder.Web.Mvc;

public class TextWidgetProperties : IWidgetProperties
{
    [ExcludeFromAiraTranslation]
    public string Text { get; set; } = string.Empty;
}
```

## Configure AIRA content generation and refinements

AIRA content generation and refinements allow editors to quickly generate and refine content in text-based fields in [pages](https://docs.kentico.com/documentation/business-users/website-content.md), [emails](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md), [content items](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md), and [headless items](https://docs.kentico.com/documentation/business-users/headless-content.md). AIRA makes use of the available context from the item to simplify editors' work and provide relevant content.

### Prerequisites

- Make sure that the [AIRA setting](#manage-aira-features) _Content generation and refinements_ is enabled.
- Optional configuration: If you want to use a specific tone of voice for generation, [adjust it](#adjust-the-tone-of-voice) in the AIRA application.

### Enable content generation for a content type field

The feature is available for content type fields with the _Text_, _Long text_, and _Rich text (HTML)_ data types. To enable the feature:

1. Open the **Content types** application.
2. Select a content type.
3. On the **Fields** tab, select and expand the field for which you want to enable content generation.
4. In the **AIRA features** section, add the _Generate content_ AIRA feature.
5. Select **Continue**.
6. Specify instructions for generation of text content in this field and **Save** them.
7. **Save** the changes and repeat as necessary.
8. Make sure that at least one field is [used as context for generation](#include-or-exclude-fields-from-the-context).

### Configure the context for generation

AIRA uses information from the item to generate relevant content. The context for generation can include:

- **Fields of the item** – fields of the following data types can be included: _Text_, _Long text_, _Rich text (HTML)_, _Date_, _Date and time_, _Pages and reusable content_. By default, new fields of these types are automatically used as context unless you [change](#include-or-exclude-fields-from-the-context) the configuration.
- **Linked items** – added by including fields where the items are linked (fields of the _Pages and reusable content_ data type). AIRA then uses the context-enabled fields of the directly linked items. Fields of items linked further down the chain are not included.
- **Page preview** – for [pages](https://docs.kentico.com/documentation/business-users/website-content.md) included in routing, the page preview can be used as context. See [Use page preview as context for content generation](#use-page-preview-as-context-for-content-generation).

We recommend excluding fields that do not hold relevant content and could lower the quality of the generated content.

AIRA also takes into account the instruction specified when [adding the feature to the field](#enable-content-generation-for-a-content-type-field) and other information about the field, such as its name and size limit.

> **Note:** For the automatic in-place generation to work, at least one field needs to be [configured as context for generation](#include-or-exclude-fields-from-the-context) and filled in when the editor attempts to generate the content. Alternatively, the generation also works when [page preview](#use-page-preview-as-context-for-content-generation) is enabled as context. Otherwise, editors can only use the option to [generate content with a custom prompt](https://docs.kentico.com/documentation/business-users/aira.md#generation-and-refinements-options) in the AIRA chat.

#### Include or exclude fields from the context

To modify the generation context for an existing content type:

1. Open the **Content types** application.
2. Select a content type.
3. On the **Fields** tab, select a field to include or exclude in the context for content generation.
   - Fields with the following data types can be used as context: _Text_, _Long text_, _Rich text (HTML)_, _Date_, _Date and time_, and _Pages and reusable content_.
4. In the **AIRA features** section, select or clear the **Use field's content as context for AIRA content generation** checkbox.
5. **Save** the field.
6. Make sure that at least one field remains included in the context in order for the generation to work.

#### Use page preview as context for content generation

> **Warning:** **Network access required**
>
> Using the page preview as context requires the server to access the public URL of your website. If the environment restricts this access, for example through firewall rules or authentication requirements, the feature may not function correctly. Make sure the server can reach its own public URL without restrictions.

For pages [included in routing](https://docs.kentico.com/documentation/developers-and-admins/development/routing/content-tree-based-routing.md), you can use the page preview as an additional source of context for content generation. This is useful for pages where key content is stored in Page Builder components rather than in content type fields.

To enable page preview as context:

1. Open the **AIRA** application.
2. Switch to the **Content generation** tab.
3. In the **Use page preview as context for content generation** section, select the page content types for which AIRA should use the page preview as context.
4. **Save** the settings.

When enabled, all text from the page preview is included in the context for generation.

> **Info:** **Remarks**:
>
> - For newly created pages, the preview is available only once the page is saved. Since saving requires filling in all required fields, the page preview cannot serve as context for generating content in those required fields. If no other fields are [included as context](#include-or-exclude-fields-from-the-context), automatic generation is not available until the required fields are filled in manually.
> - If you include both content type fields and the page preview in the context for generation, the field content may be duplicated — once from the field itself and once from the preview. This can lower the quality of the generated content. Consider using either fields or the page preview as context, not both.

## Rich text refinements in Page Builder and Email Builder

In Page Builder and Email Builder, the rich text editor can appear directly on the respective builder tabs as an [inline editor](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/widgets-for-page-builder/rich-text-inline-editors.md) or in the configuration dialog for component properties.

[Rich text editor refinements](https://docs.kentico.com/documentation/business-users/aira.md#rich-text-editor-refinements) are automatically enabled for the rich text inline editor. Refinements in this context can be deactivated by [disabling the Content generation and refinements feature](#manage-aira-features). Refinements in the property configuration dialog need to be [enabled](#enable-rich-text-refinements-in-property-configuration-dialog) by developers.

### Enable rich text refinements in property configuration dialog

To enable rich text refinements in the configuration dialog, apply the `FormComponentConfiguration` attribute with `AiraTextRefinementConfigurator` as the configurator type to component properties that use the rich text editor as their editing component.

The example below shows how to enable text refinements for a Page Builder widget property:

```csharp title="MyWidgetProperties.cs"
using Kentico.Xperience.Admin.Base;
using Kentico.Xperience.Admin.Base.FormAnnotations;
using Kentico.PageBuilder.Web.Mvc;

public class MyWidgetProperties : IWidgetProperties
{
    
    [RichTextEditorComponent]
    // Enables AIRA rich text refinements for the rich text editor editing component
    [FormComponentConfiguration(typeof(AiraTextRefinementConfigurator))]
    public string RichText { get; set; }
}
```