> 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/policies.md).
# Policies
## Creating a Data Protection Policy
Creating a new data protection policy is the first step in configuring security within the infrastructure covered by the system installation. Policies are a set of rules that enable implementation of various data protection scenarios, such as managing file operations, monitoring events, or responding to specific situations. By flexibly assigning objects and users and defining rules, administrators can precisely tailor actions to the organization’s needs.
Button **+ Add policy** in the data protection policies view opens the configuration menu where key settings for the policy being created can be defined. The creation process includes:
1. **Naming and describing the policy** – ensuring uniqueness and easy identification.
2. **Assigning objects and users** – defining the scope of the policy.
3. **Activating the policy** – the option to enable it already during creation.
After entering the required information and configuring settings, the user proceeds to the next step, which is creating rules within the policy.
## **New data protection policy step by step**
{% stepper %}
{% step %}
### Creating a new policy
* In the main data protection policies view click the button **+ Add policy**.
* A configuration menu for the new policy will slide out from the right side of the screen.
{% endstep %}
{% step %}
### Entering the policy name and description
After selecting **+Add policy** slides out **side configuration menu** (from the right side of the screen)
* **Policy name** – Enter a unique policy name (required field).
* **Description** – Optionally enter a policy description to facilitate future identification.
{% endstep %}
{% step %}
### Assigning objects (computers)
In the **Target objects** select which devices the policy should be assigned to.
* All devices are selected by default.
* If you want to assign the policy only to specific computers or groups:
* Click the option **Custom**.
* Select specific devices or computer groups from the list.
{% endstep %}
{% step %}
### Assigning users
In the **Target users** specify the users to whom the policy applies.
* By default the policy applies to all users.
* If you want to assign the policy to selected individuals:
* Click the option **Custom**.
* Choose the appropriate users from the list.
* **Exclusions** - select +Add and indicate users whom the policy should not cover, despite the "Everyone" option being selected.
{% endstep %}
{% step %}
### Policy activation
In the **Status** toggle the switch to set the policy as active or leave it disabled at this stage.
* **Active policy** – automation will operate from the moment it is saved.
* **Inactive policy** – automation will remain disabled until manually enabled.
{% endstep %}
{% step %}
### Proceeding to rule creation
* After entering all required information the **Next step** button will become active.
* Click **Next step**, to proceed to configuring the first automation rule assigned to the policy.
{% endstep %}
{% endstepper %}
After creating the Data Protection Policy you can proceed to configuring [**data protection rules**](/eacloud-docs-en/features/data-loss-prevention-1/start/triggers.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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention-1/start/policies.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.
