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

# Repositories

The record of processing activities relies on repositories (assets, stakeholders, datasets, data fields, security measures, categories of data subjects) that you manage separately.

To limit data entry errors, Dastra lets you manage repositories independently from the record of processing activities. The processing activities of the record then reuse the elements of these repositories.

## Access the repositories

In the side menu, under **Data inventory**, click **Repositories**. The menu offers:

* **Overview**: the number of elements in each repository.
* **Graphs**: a graphic representation of your assets and stakeholders.
* **Assets**, **Stakeholders**, **Datasets**, **Data glossary**, **Measures** and **Cat. of data subject**: the six repositories.

What you can do depends on the data mapping and repositories permissions of your role. See [Roles and permissions](https://doc.dastra.eu/en/features/settings/roles.md).

## The six repositories

* [Assets](https://doc.dastra.eu/en/features/mapping/repositories/assets.md): data media, premises, and tangible or intangible equipment.
* [Stakeholders](https://doc.dastra.eu/en/features/mapping/repositories/stakeholders.md): the companies and people linked to your processing, which do not need to sign in to the platform.
* [Datasets](https://doc.dastra.eu/en/features/mapping/repositories/datasets.md): groups of data fields that form coherent sets, with their retention rules.
* [Data glossary](https://doc.dastra.eu/en/features/mapping/repositories/data-glossary.md): the data fields, the most atomic level in Dastra.
* [Security measures](https://doc.dastra.eu/en/features/mapping/repositories/security-measures.md): the technical or organizational provisions that protect the data. The menu entry is **Measures**.
* [Categories of data subjects](https://doc.dastra.eu/en/features/mapping/repositories/subject-categories.md): the groups of individuals whose data you process. The menu entry is **Cat. of data subject**.

Each page describes the fields of the form, how to create, import and merge elements, and where the repository is used. How a processing activity uses these elements is described once, in the pages of the activity: see [Complete a data processing activity](https://doc.dastra.eu/en/features/ropa/activity.md).

## Features shared by the lists

The lists of the six repositories share several features:

* **Create from library...** adds an element from the template library. For most repositories, an AI button next to the create button drafts an element from a short description, when the feature is enabled for your organization.
* **Import** adds elements from a file. See [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md).
* **Export** exports the list, or only the selected lines.
* **Data quality tool** detects duplicates, and **Merge** combines them. The data quality tool does not exist for categories of data subjects. See [Merging elements](https://doc.dastra.eu/en/features/general/merge.md).
* Filters, custom columns and custom views. See [Advanced filters](https://doc.dastra.eu/en/features/general/filters.md).
* Bulk actions on a selection of lines. See [Lists, bulk actions and recycle bin](https://doc.dastra.eu/en/features/general/lists.md). **Edit fields...**, where it is offered, changes the same field on all the selected elements.
* The table and card views, for assets and stakeholders.

In the repositories, **Delete** asks for confirmation and deletes the element permanently: the recycle bin described in the lists page does not apply.

The forms also share the [custom fields](https://doc.dastra.eu/en/features/general/custom-fields.md), except for categories of data subjects, and, in the toolbar, the [generic relationships](https://doc.dastra.eu/en/features/mapping/relationships.md) of the element, where it is offered.

## Overview and graphs

The **Overview** page shows one card per repository with its number of elements. Click a card to open the matching list. The **Add an asset** button creates an asset from this page.

The **Graphs** page offers four representations, which you choose in the drop-down list at the top left:

* **Node mapping**: a graph of assets, their publishers, their datasets and their tags. [Generic relationships](https://doc.dastra.eu/en/features/mapping/relationships.md) appear as links.
* **Mapping of stakeholders**: a graph of stakeholders, their assets and their subsequent processors, which you can filter by **Responsibility**.
* **Sankey diagram**: a diagram of the distribution of data by asset, which you can filter by type (data fields, processing activities, owners, countries, data categories).
* **Hierarchy chart**.

The **Print** and **Refresh** buttons are available at the top of the page.


---

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