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

# Summary

Review all the information of a processing activity on a single page, in several views, and print it.

The **Summary** section is the last section of a processing activity. It gathers, on a single read-only page, all the information entered in the previous sections.

{% hint style="info" %}
Users who can view processing activities but are not allowed to edit them only have access to the **Summary** section.
{% endhint %}

## Choose a view

The buttons at the top of the section switch between four views. Dastra remembers the last view you selected.

* **Detailed view**: one card per section of the processing activity, from **General** to **Documentation**, with an **Impact assessment** card for a data controller activity and a **Controllers** card for a data processor activity. The first card shows the name of the processing activity, its entity and department, its tags, the **Overall progression**, **Quality** and **Sensitivity** indicators, then the internal reference, the description, the workflow state, the creation and last edit dates, the author, the version's description and the [relationships](https://doc.dastra.eu/en/features/ropa/relationships.md) with other processing activities. Click **Edit** on a card to go directly to the corresponding section, and use **Collapse all** or **Deploy all** to fold or unfold all the cards.
* **Mapping**: a diagram of the processing activity and of the elements linked to it: purposes, datasets, data subjects, assets, recipients, parties involved and, for a data processor activity, controllers. Click an element to display its details.
* **Section 30**: a table that presents the information required by Article 30 of the GDPR (description, data controller or processor, representatives, data protection officer, purposes, categories of data, data subjects, recipients, data transfers, data retention, security measures and, for a data processor activity, controllers), with the reference of the corresponding paragraph of Article 30.
* **Condensed view**: a simplified presentation of the processing activity in cards, with charts of the data, data subjects and recipients.

## Print the summary

Click **Print** to print the current view.


---

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