---
title: Associate a Relevance Generative Answering (RGA) model with a query pipeline
slug: nb6a0104
canonical_url: https://docs.coveo.com/en/nb6a0104/
collection: leverage-machine-learning
source_format: adoc
---
# Associate a Relevance Generative Answering (RGA) model with a query pipeline
When a [Coveo Machine Learning (Coveo ML)](https://docs.coveo.com/en/188/) [model](https://docs.coveo.com/en/1012/) has been created, it must be associated with a [query pipeline](https://docs.coveo.com/en/180/) to be effective in a [search interface](https://docs.coveo.com/en/2741/).

[organization](https://docs.coveo.com/en/185/) [members](https://docs.coveo.com/en/2869/) with the [required privileges](#required-privileges) can access the **Machine learning** tab of a query pipeline configuration page to manage Coveo ML model associations for that query pipeline.

When a [Relevance Generative Answering (RGA)](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated with a [query pipeline](https://docs.coveo.com/en/180/), the model is used to generate answers for [queries](https://docs.coveo.com/en/231/) that are submitted in the [search interface](https://docs.coveo.com/en/2741/) that's associated with the query pipeline.

> **Notes**
>
> * Coveo recommends that you associate only one [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) per query pipeline.
> 
> * When using [Relevance Generative Answering (RGA)](https://docs.coveo.com/en/n9de0370/), the query pipeline should be configured to use both an [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) and a [Semantic Encoder (SE) model](https://docs.coveo.com/en/nb890247/).
> 
> * To broaden the search results during [first-stage content retrieval](https://docs.coveo.com/en/n9de0370#first-stage-content-retrieval), enable the [Partial Match](https://docs.coveo.com/en/414/) feature for the query pipeline.
> 
> * To leverage RGA in your search interface, you must [enable the RGA component for your Coveo-powered search interface](https://docs.coveo.com/en/nb6a0037/).
> 
> * Query pipeline [stop word rules](https://docs.coveo.com/en/3406/) aren't applied to the query that's used by the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).
> The [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) always uses the raw [basic query expression (`q`)](https://docs.coveo.com/en/178/) entered by the user without any transformations or modifications.
> 
> * By default, query pipeline [thesaurus rules](https://docs.coveo.com/en/3405/) aren't applied to the query that's used by the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).
> Enable the [**Thesaurus rules** model association option](https://docs.coveo.com/en/nb6a0104#thesaurus-rules) to apply thesaurus rules to the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

## Associate an RGA model

> **Important**
>
> Follow the [model association leading practices](https://docs.coveo.com/en/nb6a0104#leading-practices) when associating your model with your query pipeline.

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline for which you want to associate the model, and then click **Edit components** in the Action bar.

. On the subpage that opens, select the **Machine learning** tab, and then in the upper-right corner, click **Associate model**.

. In the **Model** dropdown menu, select the desired model.

. On the right side, under **Condition**, you can select a [query pipeline condition](https://docs.coveo.com/en/2793/) in the dropdown menu or [create a new one](https://docs.coveo.com/en/1959#create-a-condition).


> **Note**
>
> An RGA model must be associated with a `Query is not empty` condition.

. Review and optionally modify the [**Advanced configuration**](#rga-model-association-advanced-configuration) options.

. Click **Associate model**.

## Edit an RGA model association

> **Important**
>
> Follow the [model association leading practices](https://docs.coveo.com/en/nb6a0104#leading-practices) when associating your model with your query pipeline.

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline for which you want to edit a model association, and then click **Edit components** in the Action bar.

. On the subpage that opens, select the **Machine learning** tab, click the desired model, and then click **Edit** in the Action bar.

. On the right side, under **Condition**, you can select a [query pipeline condition](https://docs.coveo.com/en/2793/) in the dropdown menu or [create a new one](https://docs.coveo.com/en/1959#create-a-condition).


> **Note**
>
> An RGA model must be associated with a `Query is not empty` condition.

. Review and optionally modify the [**Advanced configuration**](#rga-model-association-advanced-configuration) options.

. Click **Save**.

## Dissociate a model

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline from which you want to dissociate a model, and then click **Edit components** in the Action bar.

. On the subpage that opens, select the **Machine learning** tab.

. Click the model you want to dissociate from the pipeline, and then click **Dissociate** in the Action bar.

## RGA model association advanced configuration

You can use the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) association advanced configuration to:

* [Modify the maximum number of items](#maximum-number-of-items-to-consider) that the [RGA](https://docs.coveo.com/en/nbtb6010/) model considers when retrieving the relevant segments of text (chunks) from which to generate answers.

* [Modify the relevancy threshold](#chunk-relevancy-threshold) that's used to determine whether a segment of text (chunk) is relevant enough to be considered by the [RGA](https://docs.coveo.com/en/nbtb6010/) model for answer generation.

* [Enable or disable rich text formatting](#rich-text-formatting) for [RGA](https://docs.coveo.com/en/nbtb6010/)-generated answers.

* [Enable the query pipeline thesaurus rules](#thesaurus-rules) for the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

* [Prevent duplicate generative queries per month (GQPM)](#prevent-duplicate-gqpm-when-using-the-answer-manager) when your [RGA](https://docs.coveo.com/en/nbtb6010/)-enabled search interface is associated with an answer configuration in the Answer Manager.

> **Important**
>
> Modifying the default values for the model association advanced parameters may result in unintended model behavior following a model version upgrade.

### Maximum number of items to consider

[Relevance Generative Answering (RGA)](https://docs.coveo.com/en/nbtb6010/) uses [two stages of content retrieval](https://docs.coveo.com/en/n9de0370#relevant-content-retrieval).
First-stage content retrieval identifies the most relevant [items](https://docs.coveo.com/en/210/) in the [index](https://docs.coveo.com/en/204/), and second-stage content retrieval identifies the most relevant segments of text (chunks) from the items identified during first-stage content retrieval.
The answer is generated using the most relevant chunks.

If you find that answers are being generated using text from low relevance documents, you can use the **Items to consider** model association option to set a custom value for the maximum number of items considered during second-stage content retrieval.
For example, if you set the maximum number of items to 20, the RGA model retrieves the most relevant chunks only from the 20 most relevant items that were retrieved during first-stage content retrieval.

> **Important**
>
> This is an advanced [model](https://docs.coveo.com/en/1012/) association configuration that should be used by experienced Coveo administrators only.
> 
> The default setting of `100` provides good results in the majority of use cases.
> However, you can specify a custom value if you have a finely tuned query pipeline and you have a good understanding of the relevance hierarchy of the search results that are returned by your query pipeline configuration.
> Otherwise, if you set the value too low, there may not be enough relevant text (chunks) to generate an answer.
> 
> Modifying the default setting may result in unintended model behavior following a model version upgrade.

To set a custom value for the number of items to consider for RGA

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline to which the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated, and then click **Edit components** in the Action bar.

. Select the **Machine learning** tab.

. Double-click the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

. In the **Items to consider** dropdown list, select the maximum number of items to consider during second-stage content retrieval.

. Click **Save**.

### Chunk relevancy threshold

During [second-stage content retrieval](https://docs.coveo.com/en/n9de0370#second-stage-content-retrieval), [Relevance Generative Answering (RGA)](https://docs.coveo.com/en/nbtb6010/) retrieves the most relevant segments of text (chunks) based on semantic similarity with the query.
The relevancy threshold, however, determines whether a chunk is relevant enough to be considered by the [RGA](https://docs.coveo.com/en/nbtb6010/) model for answer generation.
Chunks that do not pass the relevancy threshold are not considered by the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/), and are not used to generate answers.

This setting essentially determines how strict the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is in considering chunks for answer generation based on relevancy.

Depending on your indexed content, the default relevancy threshold may result in one of the following scenarios:

* An answer isn't generated due to a lack of relevant chunks (threshold is too high).

* An answer is generated, but some of the chunks used to generate the answer are of lower relevance (threshold is too low).

If you find that answers aren't being generated, or answers are generated with less relevant chunks, you can use the **Chunk relevancy threshold** model association option to set a custom value for the relevancy threshold.

> **Important**
>
> This is an advanced [model](https://docs.coveo.com/en/1012/) association configuration that should be used by experienced Coveo administrators only.
> 
> The default **Medium** setting provides good results in the majority of use cases.
> However, you can modify the strictness level if you have a good understanding of your indexed content and want to fine-tune the chunk relevancy threshold that's used by the [RGA](https://docs.coveo.com/en/nbtb6010/) model.
> If you set the threshold too high, there may not be enough relevant text (chunks) to generate an answer, but if you set the threshold too low, answers may be generated with less relevant chunks.
> 
> Modifying the default setting may result in unintended model behavior following a model version upgrade.

To set the chunk relevancy threshold for the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/)

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline to which the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated, and then click **Edit components** in the Action bar.

. Select the **Machine learning** tab.

. Double-click the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

. Use the **Chunk relevancy threshold** slider to set the threshold strictness level.
A higher threshold means that a chunk needs to be highly similar to the query to be considered relevant.
A lower threshold means that chunks only need to be slightly similar to the query to be considered relevant.

. Click **Save**.

### Rich text formatting

By default, a new [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) association has the **Rich text formatting in generated answers** option enabled.
This means [RGA](https://docs.coveo.com/en/nbtb6010/) answers appear using rich text formatting, instead of plain text that displays answers with no formatting or styling.

> **Important**
>
> If you're using the [Coveo Headless library](https://docs.coveo.com/en/lcdf0493/) for your search interface, to use rich text formatting, you must also set `text/markdown` as the first value in the `contentFormat` property array for [`GeneratedResponseFormat`](https://docs.coveo.com/en/headless/latest/reference/interfaces/Search.GeneratedResponseFormat.html).
> Include `text/plain` as the last value in the array as a fallback.
> The answer is generated using the first format in the `contentFormat` property array, from left to right, that's supported by the RGA component.
> If you don't set this property, the answer is generated using plain text by default even if the **Rich text formatting in generated answers** option is enabled in the model association.

Rich text formatting makes the generated answers more visually appealing and easier to read.
RGA supports the following rich text formatting:

* Headings

* Strong and emphasized text (bold/italic)

* Inline and multi-line code blocks

* Quote blocks

* Ordered and unordered lists

* Tables

**Examples**

The following are examples of a generated answer with rich text formatting.

![Relevance Generative Answering rephrase](https://docs.coveo.com/en/assets/images/leverage-machine-learning/rga-rich-text-example-1-without-rephrase-buttons.png)

![Relevance Generative Answering rephrase](https://docs.coveo.com/en/assets/images/leverage-machine-learning/rga-rich-text-example-2-without-rephrase-buttons.png)

To enable or disable rich text formatting for RGA-generated answers

> **Important**
>
> If you're using the [Coveo Headless library](https://docs.coveo.com/en/lcdf0493/) for your search interface, to use rich text formatting, you must also set `text/markdown` as the first value in the `contentFormat` property array for [`GeneratedResponseFormat`](https://docs.coveo.com/en/headless/latest/reference/interfaces/Search.GeneratedResponseFormat.html).
> Include `text/plain` as the last value in the array as a fallback.
> The answer is generated using the first format in the `contentFormat` property array, from left to right, that's supported by the RGA component.
> If you don't set this property, the answer is generated using plain text by default even if the **Rich text formatting in generated answers** option is enabled in the model association.

> **Note**
>
> If you disable the **Rich text formatting in generated answers** option, the generated answers are displayed using plain text, with no formatting or styling.

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline to which the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated, and then click **Edit components** in the Action bar.

. Select the **Machine learning** tab.

. Double-click the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

. Enable or disable **Rich text formatting in generated answers**.

. Click **Save**.

### Thesaurus rules

[Enable the **Thesaurus rules**](#thesaurus) model association option to use the [query pipeline](https://docs.coveo.com/en/180/)'s [thesaurus rules](https://docs.coveo.com/en/3405/) in the associated [RGA](https://docs.coveo.com/en/nbtb6010/) model.

Extending your existing thesaurus rules to the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) can improve answer rates and overall answer quality, especially in organizations that feature domain-specific terminology or jargon.
It allows the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) to more effectively handle user queries that include a synonym or alias already defined in your thesaurus based on your specific business rules.

RGA supports the following types of thesaurus rules:

* [Synonym](https://docs.coveo.com/en/3405#synonym)

* [One-way synonym](https://docs.coveo.com/en/3405#one-way-synonym)

* [Replace](https://docs.coveo.com/en/3405#replace)

When a thesaurus rule is applied to an [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/), the query that's used by the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) for [content retrieval](https://docs.coveo.com/en/n9de0370#second-stage-content-retrieval) and [answer generation](https://docs.coveo.com/en/n9de0370#answer-generation) is modified to include the synonym or replacement term.
This helps the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) retrieve relevant content that uses terminology that differs from the user's query but that you've defined as an acceptable synonym or replacement.
During answer generation, the modified query is included in the prompt to the generative LLM, which allows the LLM to recognize the synonyms or replacement terms in the chunks when generating the answer.

* For a Synonym or One-way synonym thesaurus rule, the synonyms are added to the query using an OR syntax.
For example, if a Synonym thesaurus rule is configured as `Include cat, feline, kitten when any are present`, the query `organic cat treats` becomes `organic (cat OR feline OR kitten) treats`.
If a One-way synonym thesaurus rule is configured as `Include feline, kitten when cat is present`, the query `organic cat treats` becomes `organic (feline OR kitten) treats`, but the query `organic feline treats` remains unchanged.

* For a Replace thesaurus rule, the query includes the replacement term instead of the original term.
If the rule includes more than one replacement term, all replacement terms are added using an OR syntax.
For example, if the Replace thesaurus rule is configured as `Replace cat with feline, kitten`, the query `organic cat treats` becomes `organic (feline OR kitten) treats`.

**Example**

For the query, `What's an event recommendation`:

* Without a thesaurus rule, no answer is generated because the indexed items use the term `content recommendation` instead of `event recommendation`.
The relevance of the retrieved content is too low to be used for answer generation.

* When using a **Synonym** thesaurus rule that includes `content recommendation` and `event recommendation` when either term is present in the query, the modified query (`What's an (event recommendation OR content recommendation)`) allows the [model](https://docs.coveo.com/en/1012/) to retrieve relevant content from which an answer is generated.

![Relevance Generative Answering thesaurus rules provide answer | Coveo Machine Learning](https://docs.coveo.com/en/assets/images/leverage-machine-learning/thesaurus-rga-answer.png)

When the **Thesaurus rules** option is disabled, the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) uses the raw [basic query expression (`q`)](https://docs.coveo.com/en/178/) entered by the user without any transformations or modifications.

> **Notes**
>
> * [RGA](https://docs.coveo.com/en/nbtb6010/) doesn't support the [**Match terms exactly**](https://docs.coveo.com/en/3405#match-terms-exactly) thesaurus rule type.
> All thesaurus rules of that type are ignored by the [RGA](https://docs.coveo.com/en/nbtb6010/) model.
> 
> * If more than one rule exists in the [query pipelines](https://docs.coveo.com/en/180/) thesaurus, the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) uses only the first matching rule from top to bottom.
> You can [reorder thesaurus rules](https://docs.coveo.com/en/3405#change-the-rule-order) to prioritize certain rules over others.
> 
> * An [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) applies a thesaurus rule only to the first matching term in the query.
> All other matching terms in the query are ignored.
> For example, if a Replace thesaurus rule is configured as `Replace laptop, notebook with computer, device`, the query `Does the AD456 notebook laptop support docking stations` becomes `Does the AD456 (computer OR device) laptop support docking stations`.
> The query isn't modified to `Does the AD456 (computer OR device) (computer OR device) support docking stations` because only the first matching term (`notebook`) triggers the thesaurus rule.
> 
> * [RGA](https://docs.coveo.com/en/nbtb6010/) doesn't support a thesaurus rule that includes a condition, or that uses a [regular expression (regex)](https://docs.coveo.com/en/3405#use-java-style-regular-expressions) in its configuration.
> Such thesaurus rules are ignored by the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

> **Important**
>
> Coveo doesn't validate customer-defined thesaurus rules.
> Customers are responsible for configuring, testing (for example, using [A/B tests](https://docs.coveo.com/en/3255/)), monitoring, and maintaining these rules.
> Inefficient or ill-defined rules may negatively affect the accuracy and relevance of generated answers.
> Coveo doesn't provide tools to validate the quality of generated answers at scale.
> Customers must implement their own validation and QA processes.

To enable thesaurus rules for an associated [RGA](https://docs.coveo.com/en/nbtb6010/) model

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline to which the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated, and then click **Edit components** in the Action bar.

. Select the **Machine learning** tab.

. Double-click the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

. Enable **Thesaurus rules**.

. Click **Save**.

### Prevent duplicate GQPM when using the Answer Manager

If you [associated your RGA-enabled search interface with an answer configuration in the Answer Manager](https://docs.coveo.com/en/p5db9314/), add the `answerAPI` condition to the query pipeline's [RGA](https://docs.coveo.com/en/nbtb6010/) model association to prevent duplicate [generative queries per month (GQPM)](https://docs.coveo.com/en/nc5e0379/).

When a search interface is linked to an answer configuration, the query goes through the Search API as all queries normally do.
However, in addition to the Search API, the query also goes through the Answer API.
The Answer API is used by the answer configuration to display [feedback on the generated answers](https://docs.coveo.com/en/p5db0180/) and apply any [rules](https://docs.coveo.com/en/p5db0039/) created in the answer configuration.

Adding an `answerAPI` condition to the query pipeline's [RGA](https://docs.coveo.com/en/nbtb6010/) model association ensures that only the query in the Answer API is used to request generated answers from [RGA](https://docs.coveo.com/en/nbtb6010/).
Otherwise, both query streams would make requests to the [RGA](https://docs.coveo.com/en/nbtb6010/) model, which results in a duplicate generative query.

> **Important**
>
> If an [RGA](https://docs.coveo.com/en/nbtb6010/)-enabled search interface is no longer associated with an answer configuration, [remove the `answerAPI` condition](https://docs.coveo.com/en/nb6a0104#remove-the-answerapi-condition) for your [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) in your query pipeline.
> Otherwise, your search interface won't use the [RGA](https://docs.coveo.com/en/nbtb6010/) model and answers won't be generated.

To add the `answerAPI` condition

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline to which the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated, and then click **Edit components** in the Action bar.

. Select the **Machine learning** tab.

. Double-click the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

. Under **Condition**, add a `Context[answerAPI] is true` condition.
To do so, either select the condition from the dropdown menu if it was created previously, or click **Create a new condition** and perform the following steps:

.. In the **Add a condition** panel, click the first dropdown menu, and then select **Context**.

.. For **Context key**, enter `answerAPI`.

.. For **Context type**, select **Boolean**.

.. Click the second dropdown menu, and then select the **Is** operator.

.. Select **True**.

![Relevance Generative Answering condition | Coveo Administration Console](https://docs.coveo.com/en/assets/images/leverage-machine-learning/rga-model-association-context.png)

.. Click **Add condition**.

. Click **Save**.

#### Remove the `answerAPI` condition

If an RGA-enabled search interface is no longer [associated with an answer configuration](https://docs.coveo.com/en/p5db9314/), remove the `answerAPI` condition for your [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) in your query pipeline.
Otherwise, your search interface won't use the [RGA](https://docs.coveo.com/en/nbtb6010/) model and answers won't be generated.

To remove the `answerAPI` condition

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline to which the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/) is associated, and then click **Edit components** in the Action bar.

. Select the **Machine learning** tab.

. Double-click the [RGA](https://docs.coveo.com/en/nbtb6010/) [model](https://docs.coveo.com/en/1012/).

. Under **Condition**, remove the `Context[answerAPI] is true` condition.

. Click **Save**.

## Reorder model associations

The order in which [models](https://docs.coveo.com/en/1012/) appear in the query pipeline **Machine learning** tab is only relevant when multiple models of the same type are present.
If there are no duplicate model types in the list, the model order has no effect and each model will either execute or not based on its individual condition.

However, when multiple models of the same type are present, the models are evaluated sequentially from top to bottom.
Models of a given type are evaluated one after another.
The first model of a given type is evaluated and executes only if its condition is satisfied.
Evaluation then continues with each subsequent model of the same type following the same rules.
This can result in multiple models of the same type being executed for the same query.
The order in which they execute is determined by their order in the list, with each model potentially overriding the effect of the previous model of the same type.

To reorder model associations in a query pipeline

. On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page, click the query pipeline in which you want to reorder model associations, and then click **Edit components** in the Action bar.

. On the subpage that opens, select the **Machine learning** tab.

. Click the model whose position you want to change, and then use the **Move up** or **Move down** arrows in the Action bar to change the position of the model.

## Required privileges

By default, members with the [required privileges](https://docs.coveo.com/en/1832#required-privileges) can view and edit elements of the [**Models**](https://platform.cloud.coveo.com/admin/#/orgid/ai-and-ml/models/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/ai-and-ml/models/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/ai-and-ml/models/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/ai-and-ml/models/)) page.

The following table indicates the privileges required to use elements of the **Models** page and associated panels (see [Manage privileges](https://docs.coveo.com/en/3151/) and [Privilege reference](https://docs.coveo.com/en/1707/)).

[cols="3",options="header"]
|===
|Action
|Service - Domain
|Required access level

|View model associations
|Machine Learning - Models  
Organization - Organization  
Search - Query pipelines
|View

.2+|Edit model associations
|Organization - Organization  
Machine Learning - Models
|View

|Search - Query pipelines
|Edit
|===

## What's next?

[Enable the RGA component in your search interface](https://docs.coveo.com/en/nb6a0037/).