> 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/ropa/activity/assets.md).

# Assets

List the assets, internal or external to the organization, that support the processing activity.

This is where you list the assets, internal or external to the organization (applications, software, resources, buildings, etc.), that support the execution of the processing activity.

*For example, if you use CRM software, add it to this list.*

This information, **which is not mandatory for the register**, allows you to **map the application chain linking the data together**.

**The objective is to help you control the data carriers and link your assets to your data catalog.**

You can thus specify the types of data processed through this processing activity.

NB: Assets are not necessarily linked to processors. For example, it can be **software installed on your own server, without any intervention of its editor in the processing of personal data**.

## Link assets to the processing activity

1. In the **Assets** section, click **Attach asset**.
2. Search for the assets to link and select them. If an asset does not exist yet, click **Add an asset** to create it.

The linked assets are listed in a table. For each asset, you can:

* click **Add a description** to describe the role of this asset in this processing activity;
* click **Sync data** to import the asset's data into the processing activity (see below);
* use the **...** menu to **Edit** the asset or **Delete** it from the processing activity.

## Sync the asset data with the processing activity

An asset can already be documented in your data mapping, with its editor, its datasets and its security measures. Instead of entering this information again, you can copy it into the processing activity.

1. On the asset's row, click **Sync data**. The **Sync asset data with data processing** window lists the elements that would be added to the processing activity:
   * **Asset's editor to add as a processor**, with its transfer countries;
   * **Dataset related to this asset**;
   * **Subject categories** of the selected datasets;
   * the security measures of the asset.
2. Select the elements to add, or check **Select all**.
3. Click **Add**.

The selected elements are added to the corresponding sections of the processing activity: the editor becomes a recipient of the **Processors** category in the **Recipients** section, the datasets are added to the **Datasets** section, the subject categories to the **Data subject** section and the security measures to the **Measures** section. If a country is set for the asset or its editor, a transfer to this country is also added to the recipient: check it in the **Recipients** section.

The asset's row shows whether its data is **Synced**, **Not synced**, or when it was last synced if the asset has changed since.


---

# 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/ropa/activity/assets.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.
