> 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/editer-le-registre/data-visualization/view-the-processing-activity-tree.md).

# View the processing activity tree

## Introduction

In Dastra, data can be visualized in several ways. One of them is the visualization of **the** processing activity **tree** by entities and departments.

This visualization allows you to understand to which entities and/or departments the processing activities are attached.

## View the processing activity tree

To view the processing activity tree, click on the "Record of processing activities" module and then click on the arrow to the right of the button, to select the "Tree view" option.

<figure><img src="/files/tseYBVI8RVFDUhNB2BNC" alt=""><figcaption><p>Arrow on the right of the button &#x26; drop down menu</p></figcaption></figure>

Thus, you will be able to visualize **the tree of** processing activities.

<figure><img src="/files/zVaqTJMiqdVXr63bA50d" alt=""><figcaption><p>The processing activity tree in Dastra</p></figcaption></figure>

{% hint style="info" %}
The filters and the settings button will allow you to modify the tree view to your liking.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.dastra.eu/en/features/editer-le-registre/data-visualization/view-the-processing-activity-tree.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.