> 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.md).

# Data Mapping

Learn how to map your organization's personal data in Dastra

## It all starts with data mapping

Before you create your processing activities, map your organization's data as accurately as you can. In the application, this module is called **Repositories**. The mapping links four kinds of elements: the publisher of an asset, the asset itself, the security measures applied to it, and the datasets it holds, which are made of data fields.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6cdf445cb0dc8f9b1253452d805f863c89d8b3f7%2Fmapping-schema-1.png?alt=media" alt="Data mapping diagram: the publisher provides assets, which are linked to security measures and to datasets made of fields"><figcaption><p>Structure of the data mapping</p></figcaption></figure>

To inventory all the personal data of your information system, follow this procedure:

1. **Identify the assets**: software, files, plugins, servers, machines, etc.
2. **Identify the publisher of the asset, if applicable**: enter the details of the company that produces this asset. It can then be listed among your processors when you build the record of processing activities.
3. **Inventory the data**: list the associated datasets (you can refer to the DPA signed with the processor). For more information, see [Datasets and retention](https://doc.dastra.eu/en/features/ropa/activity/datasets.md).
4. **List the security measures** in place.

This mapping makes it easier to create processing activities, because you start from the reality of your data.

If you prefer not to build this inventory, or if the software you use is standard, create your asset repository from the library of predefined templates, which contains common assets on the market (Salesforce, Jira, etc.).

To follow one flow from the vendor to the processing activity, see [Map a data flow](https://doc.dastra.eu/en/examples/examples/data-mapping.md).

## Access the data mapping

1. [Open your workspace](https://doc.dastra.eu/en/getting-started/setup/workspace.md#access-a-workspace).
2. In the side menu, under **Data inventory**, click **Repositories**.
3. The **Overview** page opens: one card per repository, with the number of elements it contains.

Then click the repository you want to open. For the access path, the list features shared by all repositories and the graphs, see [Repositories](https://doc.dastra.eu/en/features/mapping/repositories.md).

## The repositories of the mapping

Each repository has its own page:

* [Assets](https://doc.dastra.eu/en/features/mapping/repositories/assets.md): the software, servers and other media that hold your data.
* [Stakeholders](https://doc.dastra.eu/en/features/mapping/repositories/stakeholders.md): the processors, publishers and other companies and people you work with, and their sub-processors.
* [Datasets](https://doc.dastra.eu/en/features/mapping/repositories/datasets.md): the groups of data fields, with their retention rules.
* [Data glossary](https://doc.dastra.eu/en/features/mapping/repositories/data-glossary.md): the data fields, with their category and sensitivity level.
* [Security measures](https://doc.dastra.eu/en/features/mapping/repositories/security-measures.md): the technical and organizational measures that protect the data.
* [Categories of data subjects](https://doc.dastra.eu/en/features/mapping/repositories/subject-categories.md): the groups of people whose data you process.

To document a connection that the platform does not infer, for example an asset linked to a stakeholder, see [Generic relationships](https://doc.dastra.eu/en/features/mapping/relationships.md). To reuse these repositories in your record, see [Record of processing activities](https://doc.dastra.eu/en/features/ropa.md).

## Build your list of security measures

Security measures have their own repository (see [Security measures](https://doc.dastra.eu/en/features/mapping/repositories/security-measures.md)): enter them once, then attach them to assets in the **Attached security measures** section of the asset form. This information often appears in the DPA signed with the publisher. Prefer short names (Antivirus, Application firewall, Access controls) so that a measure can be reused from one asset to another.

## Manage your processors

A processor is a [stakeholder](https://doc.dastra.eu/en/features/mapping/repositories/stakeholders.md) in your mapping. Enter it as the **Publisher** of the asset: it can then be referenced as a processor when the asset is mentioned in a processing activity. On the stakeholder form, you can also save the processor's sub-processors, to map the whole subcontracting chain.


---

# 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.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.
