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

# Data visualization

Learn how to visualize data in Dastra

## Introduction

In Dastra, the **data** of your record of processing activities can be **viewed** in several ways:

* as a list, as cards, or as a **tree** organized by entities and departments,
* as a **data map** of the record,
* as a map of data **transfers**.

## Change the Record view

To change the way processing activities are displayed in your record, go to the **Record of processing activities** module: in the left-hand menu, click **ROPA**, then **Record of processing activities**. By default, the processing activities are displayed in the **List view**. In the toolbar, click the **arrow to the right** of the **List view** button and choose another view.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e56c3f9699422431f33054ad247bed4fa7f421ee%2Fropa-tree-1.png?alt=media" alt="List view button and its drop-down menu"><figcaption><p>The views available for the record</p></figcaption></figure>

Three views are available:

* **List view**: the standard view of the record of processing activities, as a table whose columns, sorting and filters you can adjust;
* **Cards**: one card per processing activity, with its main information and indicators;
* **Tree view**: the processing activities organized by entities and departments.

{% content-ref url="/pages/WTVoDH2lyNKy5FVm4rmS" %}
[View the processing activity tree](https://doc.dastra.eu/en/features/ropa/visualization/tree.md)
{% endcontent-ref %}

## View the mapping of your record and transfers

The record data map and the transfers map are available from the left-hand menu, under **ROPA**: click **Graphs** or **Transfers**. The **Transfers** entry is displayed when the transfers map is enabled for your workspace.

{% content-ref url="/pages/k119g4KHs2eZz2G1gYVL" %}
[View the record data map](https://doc.dastra.eu/en/features/ropa/visualization/data-map.md)
{% endcontent-ref %}

{% content-ref url="/pages/Q0R6T4GQWMUWmJ7hXoJJ" %}
[View the transfers map](https://doc.dastra.eu/en/features/ropa/visualization/transfers-map.md)
{% endcontent-ref %}

## Go further

{% content-ref url="/pages/RSH8fdsWx5KSZkjvXf9a" %}
[Risk management](https://doc.dastra.eu/en/features/risks.md)
{% endcontent-ref %}


---

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