> 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-add-a-data-supplier.md).

# How to add a data supplier

A guide to creating a data supplier and inviting its users to the portal

A data supplier is the organisation you collect product data from. When you create one, you decide which areas it works in, which languages and segments it can see, how its changes are reviewed and who from the supplier can sign in.

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

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

* You need the **Manage data onboarding** permission.
* The supplier needs at least one area to work in. You can create one while creating the supplier, but it is easier to set up your [areas](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-create-areas.md) and [submission templates](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-create-submission-templates.md) first.
  {% endhint %}

## How to create a data supplier

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

![The data supplier list](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FqFxYhmsRk2worRza7UBh%2Fdop-supplier-list.png?alt=media)

This opens a wizard with five steps. **Next** stays disabled until the current step is filled in correctly, and nothing is saved until you click **Create supplier** on the last step.

### Step 1: General settings

![Step 1: General settings](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FQuZVk1SMuP5iYDsNM03K%2Fdop-wizard-general.png?alt=media)

* **Name** is the supplier organisation's name.
* **Identifier** is filled in from the name. Click the pencil to edit it. The identifier cannot be changed after the supplier is created.
* **Description** is optional internal notes. Suppliers do not see it.
* **Responsible** is the people in your organisation who own this supplier. They are notified when the supplier writes in a feedback thread.
* **Media archive folder** is where media uploaded by the supplier is stored. Leave it empty if the supplier should not upload media.

### Step 2: Areas

Assign the areas the supplier works in. A supplier only sees the products of its assigned areas.

Click **Assign area** and pick an area from the list. If the area you need does not exist yet, click **Create area** at the bottom of the list.

![Assigning areas and setting values for the supplier](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FGw6e0taQAZYpmzo91D2H%2Fdop-supplier-areas.png?alt=media)

If the area leaves some conditions open, for example a brand, fill them in under **Values for this supplier**. The values apply to this supplier only.

**What this supplier gets** previews the result with your values filled in, and counts how many products, variant groups and variants the supplier will see.

{% hint style="warning" %}
A level grants nothing until every value is set. You cannot continue until every assigned area has all its values.
{% endhint %}

### Step 3: Languages & segments

Choose the languages and segments the supplier can see and edit. Turn on **Read only** for a language or segment the supplier should see but not change.

![Languages and segments](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FOzDjZE3Ll7mblBmvLx7y%2Fdop-supplier-languages-segments-v2.png?alt=media)

You need at least one language, and at least one segment in every dimension that has segments.

### Step 4: Review policy

By default, every attribute follows the review setting in its submission template. This step is optional, and you only need it when this supplier should be treated differently.

* Turn on **Review everything from this supplier** to send all of the supplier's changes to review, whatever the templates say.
* Click **Add attributes** to make exceptions for single attributes. An exception starts at the opposite of what the template says, and you can switch it between **Requires review** and **Merge directly**.

![Review policy with an exception](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FM3Eo0WXxBc0ZbYm4z9H1%2Fdop-supplier-review-policy.png?alt=media)

The **Template says** column shows the template's setting. If the supplier's areas use templates that disagree, it shows **Mixed**.

### Step 5: Invited users

Add the people from the supplier who should sign in to the portal. This step is optional, and you can invite users later.

Click **Add user** and enter their **Email**, **Display name** and **Role**:

* **Admin** manages the supplier's team and submissions in the portal
* **Editor** edits the supplier's product data
* **Viewer** can only read the supplier's product data

The first user is an admin by default. A supplier should always have at least one admin, so that someone can manage its team.

Click **Create supplier** to finish. Each invited user receives an email with a link to set their password. The link expires after 2 days, and you can send a new one at any time. The email is how suppliers find the portal. You can also share the link yourself. It is under **Portal settings > Portal address**.

{% hint style="info" %}
An email address can only be used by one supplier login in your Struct PIM. If a colleague is also a PIM user, they get a separate supplier login with its own password, and choose "I'm a supplier" when signing in to the portal.
{% endhint %}

## How to edit a data supplier

Click the supplier in the list to open it. The edit page has the same settings as the wizard, split into tabs. Each tab is saved on its own with **Save**.

On the **General settings** tab you can also change the supplier's **Status**. A disabled supplier cannot sign in to the portal.

## How to manage the supplier's users

Open the **Invited users** tab to see everyone who can sign in for the supplier, their status and when they were last active.

![The supplier's Invited users tab](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FReim0pheTv2E3cDodXxA%2Fdop-supplier-invited-users.png?alt=media)

* Click **Create supplier login** to invite another user.
* Use **Resend invite** if a user did not receive their email, or their link expired.
* Use **Sign out everywhere** to end all sessions of one user, for example if their device is lost.
* Use **Sign everyone out** to sign out every user of the supplier at once, for example when you suspect an account is compromised. Work they have not saved is lost.

## How to delete a data supplier

Delete the supplier from the data supplier list, this also deletes all of its logins.

{% hint style="danger" %}
Deleting a supplier permanently removes its area assignments, feedback threads and attachments, and any changes it has not yet had merged. Values already merged into your live data stay.
{% endhint %}


---

# 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-add-a-data-supplier.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.
