> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention-1/start/risk-levels.md).
# Risk Levels
## Risk levels
The risk level defines how significant an automation rule or data protection policy is in the context of information security within the organization. This parameter allows classifying rules according to their impact on resource protection and can be used to prioritize alerts or remediation actions.
### Configuration
{% stepper %}
{% step %}
### Setting the risk level
The risk level (from 1 to 100) defines how significant an automation rule or data protection policy is for your organization. It can be adjusted by moving the slider in the upper right corner of the screen before saving the policy.
Examples:
* **Low risk level (1–33)**: Actions with low impact, e.g., a user visited a site in the social media category.
* **Medium risk level (34–66)**: Events such as a user visiting a site in the Gambling category.
* **High risk level (67–100)**: Critical events, e.g., copying a file containing personal data.
The set risk level can be changed at any stage of configuration.
{% endstep %}
{% step %}
### **Click Assign to policy**
In the upper right corner of the screen select the **Assign to policy**button to save the rule configuration.
{% endstep %}
{% step %}
### **Return to the main policies view**
After saving, the system automatically redirects the user to the main automation policies view, where the new rule is visible within the created policy.
{% endstep %}
{% endstepper %}
---
# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention-1/start/risk-levels.md?ask=&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.
