> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configurations

> Name a configuration, assign intents and areas, and understand how the three field tabs work together.

## Overview

Each field configuration defines the fields that appear in Flow for a specific combination of intent and area. When a request arrives, Go Autonomous matches it to the right configuration and uses those fields for extraction, display, and confirmation.

***

## Configuration name

Enter a name that reflects the use case — for example, "Order", "Quote", or "Delivery Notice".

Validation rules:

* Name is required before saving.
* Names must be unique. If a name already exists, you'll see: *"This name already exists. Please enter a unique name."*

Click the pencil icon next to the name at any time to rename it.

***

## Selecting intents

Use the **Intents** picker to choose which request types this configuration applies to. At least one intent is required.

**Conflict rule:** If an intent is already assigned to another configuration for the same area, it will appear greyed out with a tooltip naming the conflicting area. You cannot assign the same intent + area combination to two configurations.

***

## Selecting areas

Use the **Areas** picker to choose which areas this configuration applies to. Areas are optional — leaving this blank makes the configuration the **default**, which applies to any area not covered by a more specific configuration.

**Conflict rule:** If an area is already paired with the selected intents in another configuration, it will appear greyed out with a tooltip listing the conflicting intents.

<Note>
  If you remove an area from an existing configuration, any area-specific default values that were set for fields in that configuration are automatically cleared.
</Note>

Once an area is linked to a configuration, you can see which configurations are attached to it directly from the [Areas](/knowledge-base/administration/areas) page.

***

## The three tabs

Once a configuration is named and intents are set, three tabs let you define fields across different parts of the Flow interface:

| Tab            | What it controls                                                                                                                     |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Summary**    | Request-level fields shown in the Summary panel — header details, delivery address, account information, and other order-level data. |
| **Line Items** | Fields shown per product row in the product cart — the columns your team uses to review and edit extracted line items.               |
| **Stocklines** | Fields shown within the stockline (subproduct) viewer — additional detail about each product variant or sub-item.                    |

Each tab is independent. You can have different fields, different visibility settings, and a different layout on each.

[Learn more about configuring each tab →](/knowledge-base/administration/fields-manager/tabs)

***

## Unsaved changes

If you navigate away from a configuration with unsaved changes, a dialog appears:

> *"This will discard all unsaved changes. In order to not lose your changes, save your configuration first."*

Click **Save configuration** in the top toolbar to commit your changes before leaving.

***

## What's next

* [Summary, Line Items, and Stocklines tabs](/knowledge-base/administration/fields-manager/tabs)
* [Adding and configuring fields](/knowledge-base/administration/fields-manager/adding-fields)