> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/mapping/repositories/stakeholders.md).

# Stakeholders

Record the companies and people you work with (processors, publishers, recipients, DPO, customers), their sub-processors and the assets they publish.

Stakeholders are the companies and individuals linked to your data processing: processors, software publishers, AI model providers, joint controllers, public bodies, customers, and so on. Unlike users, they do not sign in to Dastra.

Enter each stakeholder once in this repository. Assets, processing activities, contracts and data breaches then reference it, so a change to its details applies everywhere.

## Add a stakeholder

Open **Data inventory** > **Repositories** > **Stakeholders**. You can:

* click **Create stakeholder**, then choose **Built-in template** to start from a template of the library, or **Personalized** to start from scratch;
* click the AI button to the left of **Create stakeholder** to describe the stakeholder and let the assistant draft it (this option depends on the features enabled for your organization);
* click the arrow next to **Create stakeholder**, then **Create from library...**;
* import stakeholders from a file: arrow next to **Create stakeholder**, then **Import**. See [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md);
* turn emails into stakeholders: arrow next to **Create stakeholder**, then **Transform emails to stakeholders**. This opens the incoming mail integration of the workspace settings.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a00b31719194f5ff05ad72cee22e06124d4ce5e7%2Frepositories-stakeholders-1.png?alt=media" alt="List of stakeholders with the Create stakeholder menu open"><figcaption><p>The list of stakeholders</p></figcaption></figure>

## Complete the stakeholder form

| Section                   | Field                                           | Content                                                                                                                                                                                                               |
| ------------------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **General information**   | **Person** or **Company**                       | The nature of the stakeholder. The name field is **Full name** for a person and **Company's name** for a company, required.                                                                                           |
|                           | **Internal reference**, **Organizational unit** | Your reference, and the unit that can see the stakeholder. Without a unit, all units see it.                                                                                                                          |
|                           | **Stakeholder owner**                           | The user in charge of the stakeholder.                                                                                                                                                                                |
|                           | **Description/Biography**, **Website url**      | A free description and the address of the website.                                                                                                                                                                    |
|                           | **Company registration number**                 | Company only. When the SIRET integration is enabled, you can search the SIRET database and the address is filled in for you.                                                                                          |
|                           | **Address**                                     | **Country**, **Address**, **City**, **Postcode** and **State/Province/Region**.                                                                                                                                       |
|                           | **Contact details**                             | **Contact name**, **Contact job title**, **Contact email** and **Contact phone number**.                                                                                                                              |
| **Subsequent processors** |                                                 | The sub-processors of the stakeholder, often named in the DPA. Select them in the list or create them, then enter the **Data location country** and a description for each. This maps the whole subcontracting chain. |
| **Related assets**        |                                                 | The assets published by the stakeholder. Selecting an asset makes the stakeholder its **Publisher**: if the asset already has another publisher, Dastra asks you to confirm the replacement.                          |

The [custom fields](https://doc.dastra.eu/en/features/general/custom-fields.md) defined for stakeholders are added to the form, and you can attach a logo and [tags](https://doc.dastra.eu/en/features/general/tags.md).

The toolbar of the form gives access to the attached documents, comments, questionnaires, tasks, contracts and risks linked to the stakeholder, depending on your permissions and the enabled features. It also contains:

* **Linked elements**: the [generic relationships](https://doc.dastra.eu/en/features/mapping/relationships.md) of the stakeholder;
* **Related processing**: the processing activities that use the stakeholder, with a **Link to data processing** button to add more;
* **Activity history**;
* the regular review of the stakeholder. See [Regular review (freshness)](https://doc.dastra.eu/en/features/regular-review.md);
* the workflow step of the stakeholder, when workflow steps are defined.

The actions menu of the form offers **Create a copy**, **Merge**, **Export** and **Delete**.

## Find stakeholders in the list

Besides the filters described in [Repositories](https://doc.dastra.eu/en/features/mapping/repositories.md), the list offers:

* the **Responsibility** filter: software publisher (publisher of at least one asset), AI model provider (publisher of at least one AI model), or recipient in a processing activity (processor, joint controller, public body, etc.);
* the **Type**, **Country**, **Steps** and **Filter by tags** filters, and the organizational unit;
* the table and card views;
* the **Subsequent processors** and **Related contracts** columns, hidden by default, in **Customize columns**.

From a selection, the bulk actions include **Link to data processing**, **Send questionnaires**, **Review**, **Merge** and **Export**.

## Where stakeholders are used

* In a processing activity, a stakeholder can be a data controller, a joint controller, a processor or another recipient. See [Stakeholders](https://doc.dastra.eu/en/features/ropa/activity/stakeholders.md) and [Recipients](https://doc.dastra.eu/en/features/ropa/activity/recipients.md) of the activity.
* As the **Publisher** of an asset. See [Assets](https://doc.dastra.eu/en/features/mapping/repositories/assets.md).
* In contracts, data breaches, risks and questionnaires.

{% hint style="warning" %}
Deleting a stakeholder removes its references in processing activities (recipients, data controller, stakeholder), incidents, organizational units and discussions. Tasks, questionnaires and attached files are kept.
{% 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://doc.dastra.eu/en/features/mapping/repositories/stakeholders.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.
