> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-enrichment-insights/how-to-set-up-and-edit-an-enrichment.md).

# How to set up and edit an enrichment

This tutorial goes through the process of setting up and editing an enrichment.

### Set up an enrichment insight

To create a new Enrichment Insight, navigate to 'Settings' and click 'Enrichment Insights'. Now click the 'Create Enrichment Insight'-button in the top-right corner to open the creation menu.

<figure><img src="https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FXKcqb3v0LTncW9NmH5PX%2Fimage.png?alt=media&amp;token=20e6a831-d793-4e14-a788-5261eeac446a" alt="The Enrichment Insight page"><figcaption><p>Enrichment insights page</p></figcaption></figure>

We will create an enrichment for dangerous goods within the product catalogue to make sure they live up to the rules and guidelines for storing, selling and distributing dangerous goods.

An enrichment insight is applied to a specific entity type. These types include: [variants](/fundamental-concepts/data-management.md), variant groups, [categories](/fundamental-concepts/data-model.md), assets and [products](/fundamental-concepts/data-management.md). Select the one that you would like to make an enrichment insight for.

Aliases can not contain spaces, a good rule of thumb when setting the alias is using a concatenation of the label.

**Label:** Dangerous Goods Enrichment

**Alias:** DangerousGoodsEnrichment

<figure><img src="https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2Fak8EJJ7X0lEmsZf9zme3%2Fimage.png?alt=media&amp;token=59b01c22-6edc-46c4-8c93-bbcef0d9009c" alt=""><figcaption><p>Create enrichment insight page</p></figcaption></figure>

Before adding enrichment rules, make sure to define a clear and descriptive label and alias. This will help avoid confusion about the purpose of the enrichment insight. Once the label and alias are set, proceed to add the enrichment rules accordingly.

### Edit an enrichment insight

To edit an enrichment insight, go to 'Settings' and click on 'Enrichment insights'. Here you will find all the insights created. You can filter the insights by typing values into the column headers.

When you have found the enrichment insight you would like to edit, hover over the row and click the <i class="fa-pen">:pen:</i>-Icon.

<figure><img src="https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2F7QY8zKwyuozEsuAt0XaN%2Fimage.png?alt=media&amp;token=82374530-9d53-4608-a9c3-465a911eb353" alt=""><figcaption></figcaption></figure>


---

# 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://docs.struct.com/tutorials/guides/how-to-use-enrichment-insights/how-to-set-up-and-edit-an-enrichment.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.
