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

# FAQ

## Why does the Risk management menu not appear?

The module must be enabled for your workspace, and your role must include read access to risks. Creating or editing a risk requires write access. Contact your workspace administrator.

## Why can't I move a risk to the next step?

Only the owner of a risk can change its state: validate the assessment, validate the response, archive it or go back to a previous step. The owner's name is shown in the **Identification** section of the risk. To hand the risk over to someone else, change the **Risk owner** in that section.

## What is the difference between initial, residual and current risk?

The initial risk is the risk before any control measure. The residual risk is the one you aim for once the measures are in place. The current risk sits between the two, according to the remediation rate of your control points. The formulas are in the [glossary](https://doc.dastra.eu/en/features/risks/glossary.md).

## Why does my current risk not change despite my control points?

Check the following:

* the response type is **Mitigation and controls**: the other options do not calculate a remediation rate;
* the risk has an initial level and a residual level;
* control points are assigned to the risk type and have received a response. A control point without a response counts zero points;
* the responses are not all **Not applicable**: these responses are excluded from the calculation.

## What happens if I change the risk scale?

Enabling another scale changes the statistics of every risk in the workspace, and Dastra asks for a confirmation before doing it. Choose your scale before entering your first risks. See [Configure the risk scale](https://doc.dastra.eu/en/features/risks/process/assess.md#configure-the-risk-scale).

## How do I assess the same risk on several processing activities or assets?

Use **Batch risk identification**: select the risk type and all the objects concerned, and Dastra creates one risk per object. See [Risk management](https://doc.dastra.eu/en/features/risks.md).


---

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