> 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/risks/attach-to-processing.md).

# Attach a risk to a processing activity

Dastra lets you map the risks linked to processing activities to quickly assess the level of priority and the actions to take on a processing activity.

## Add a risk to a processing activity

1. Open the processing activity in the record of processing activities.
2. In the row of buttons under the title, click **Risks**. The button shows the number of risks already attached to the processing activity.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-01cb64d683a0004d8b71cdfc6287a3fa060c10b9%2Frisks-attach-1.png?alt=media" alt="Processing activity page with the Risks button and its counter in the button row"><figcaption><p>The Risks button of a processing activity</p></figcaption></figure>

3. In the panel that opens, click **Create a risk**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f45c3f8b5542e09f3a0c540a879dd2655a44eaff%2Frisks-attach-2.png?alt=media" alt="Risks panel of a processing activity with the matrix, the attached risks and the Create a risk button"><figcaption><p>The Risks panel of a processing activity</p></figcaption></figure>

You land on the risk edit page, with the processing activity and its organizational unit already filled in. Start entering the information about the risk you have identified, as described in [Identify](https://doc.dastra.eu/en/features/risks/process/identify.md).

You can also attach a risk to a processing activity from the risk management module: open **Risk management** > **Risks**, choose the **Processing activity** tab and click **Create a risk**.

## View the risks of a processing activity

To see the risks of all your processing activities, open **Risk management** > **Risks** and choose the **Processing activity** tab. Each row shows the risk type, the processing activity concerned and the initial, current and residual risk levels.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-3f81068606220595b3628880515ec3bd4f6f2638%2Frisks-list-1.png?alt=media" alt="List of the risks of the Processing activity tab, with initial, current and residual risks"><figcaption><p>The risks attached to processing activities</p></figcaption></figure>

## Risk level assessment

The risk level is calculated with the following formula:

`Risk level = probability value x impact value`

Dastra shows it in points out of the scale maximum (for example 16/25) and as a percentage. The percentage is calculated with the following formula:

`(impact x probability) / maximum score of the active risk scale`

The maximum score of the scale is 25 with the default 5-level scale (5 x 5), 16 with the 4-level scale and 9 with the 3-level scale. See [Configure the risk scale](https://doc.dastra.eu/en/features/risks/process/assess.md#configure-the-risk-scale).

The workspace dashboard contains a **Risk management** module. It shows the averages, as percentages, of the initial, current and residual risk, the average remediation, the number of risks per step (**Total**, **Identified**, **Pending response**) and the breakdown of low, medium and high residual risks. Each average is based on the percentages calculated above.

## Go further

{% content-ref url="/pages/-Lw3hALWsjvX2sseOt14" %}
[Planning](https://doc.dastra.eu/en/features/tasks.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/risks/attach-to-processing.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.
