> 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-the-data-onboarding-portal/how-to-create-areas.md).

# How to create areas

A guide to deciding which products suppliers work on

An area is a part of your catalogue that you share with suppliers, for example "Bedding". It decides which products, variant groups and variants the suppliers see, and which submission template decides what they are asked for. One area can be shared by many suppliers.

Areas are found under **Settings > Data onboarding > Areas**.

{% hint style="info" %}
**Before you start**

An area needs a [submission template](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-create-submission-templates.md). You can also create one from the area page by clicking the **+** next to **Submission template**.
{% endhint %}

## How to create an area

Click **Create area** in the top-right corner of the area list.

![Creating an area](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FlBL3TErdPOm430XrUmIW%2Fdop-area-general.png?alt=media)

1. Enter a **Name**. Suppliers see areas by name, so each area needs a unique name.
2. Enter a **Description** if you want a note for your colleagues. Suppliers do not see it.
3. Choose the **Submission template**. The page tells you which levels the template asks for attributes at.
4. Set up the **Access query** to decide which products are shared. See below.
5. Click **Create area**.

### Deciding which products are shared

The access query has a tab for each level: **Products**, **Variant groups** and **Variants**.

* On **Products**, add the rules that pick the products the suppliers work with. Click **Add rule**, then **New condition**, and choose a field, an operator and a value.
* On **Variant groups** and **Variants**, you can narrow which variant groups and variants of those products are shared. Leave them empty to share all of them.

{% hint style="warning" %}
An area with no product rule shares no products at all.
{% endhint %}

A level marked **Not asked for** is one where the submission template asks for nothing, so suppliers do not see that level in the portal.

### Using one area for many suppliers

Often the rule is the same for every supplier except for one value, such as their brand. Instead of creating an area for each supplier, switch the condition's value from **Fixed** to **Dynamic**. The value then reads **Set per supplier**.

![Access query with a value set per supplier](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FkuX4zIyXGQLIILkGsRyR%2Fdop-area-access-query-v2.png?alt=media)

When you assign the area to a supplier, you are asked to fill in the value for that supplier, for example "Brand equals Fjord Textiles". Until the value is set, the supplier gets nothing from that level.

## How to choose the supplier's default columns

After the area is created, open it again and go to the **Default list columns** tab. Here you choose the columns suppliers see in their product list for each level, and their order.

Click **Add columns** to add attributes from the submission template, or portal columns such as **Status** and **Completeness**. Drag columns to reorder them. Suppliers can choose their own columns in the portal, and these defaults apply until they do.

![Default list columns for the Products level](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FsynqeGz0T2Vzv5BIzvyK%2Fdop-area-default-columns.png?alt=media)

If you choose no columns, suppliers see the name, status, completeness and open comments.

## How to edit an area

Click the area in the list, make your changes, and click **Save**.

{% hint style="warning" %}
If suppliers are assigned to the area, saving changes what they see in the portal straight away.
{% endhint %}

## How to delete an area

An area cannot be deleted while suppliers are assigned to it. Unassign it on each supplier's **Areas** tab first, then delete the area from the list.


---

# 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-the-data-onboarding-portal/how-to-create-areas.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.
