> 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/dlp-policies-and-rules/triggers/file-sent.md).
# File sent
## Trigger File Send
Trigger **Sending a file** allows monitoring and blocking of operations related to file transfers via various channels, such as:
* Email.
* Cloud application.
* Other.
With this feature, any attempt to attach or upload a file can be monitored, blocked, or logged by the system. The tool also supports file synchronization with cloud applications and other user-defined processes, such as data transfers in messaging apps (e.g., Microsoft Teams).
{% hint style="warning" %}
When monitoring operations on a file containing **specific content** or **marked with an invisible tag**, it is possible to track activity related to the file regardless of its location, extension, etc. This enables monitoring to function even when the file is moved, copied, or edited.
**To configure monitoring, first go to the** [**Document Tagging**](/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/actions/document-marking.md)**.**
{% endhint %}
## Trigger configuration
### Select transfer type
The user must specify the type of transfer operation:
* **Email:** Monitoring file transfers via email.
* **Cloud applications:** Monitoring synchronization of data with cloud applications (support for 20 types).
* **Other:** Monitoring file transfers to user-defined processes (e.g., messaging apps).
### Configuration for email
* **File and path masks:** Specifying files and locations to be monitored or blocked.
* **Exclusions:** Defining file types or paths excluded from monitoring.
* **Tags:** Optional application of previously assigned tags to limit the trigger's action to specific files. More in [Document Tagging](/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/actions/document-marking.md).
### Configuration for cloud applications
Includes all options available for email.
* **Additionally:** Selection of the cloud application used by the user.
#### **List of supported cloud applications:**
* Microsoft OneDrive
* BitTorrent Sync
* Box
* Copy
* Cubby
* Dropbox
* Google Drive
* Knowhow Cloud
* Mediafire
* Mega
* Mozy
* OwnCloud
* Spideroak
* STRATO HiDrive
* Tresorit
### Configuration for Other
Includes all options available for email. Additionally:
* **Monitored processes:** The user specifies particular processes in which file transfers should be monitored or blocked (e.g., `teams.exe`).
* **Excluded processes:** Ability to exclude selected processes from monitoring.
[How to add/edit a mask?](/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/file-operations/masks.md)
## Example of use
**Objective:** Protect the company's price list from being sent by users via various channels.
* **Configuration:**
* Select file `price_list.xlsx` as the monitoring object. (**Option 1:** Specify the file location and name; **Option 2:** Specify a previously assigned tag for this specific file – an optimal solution, resistant to copying and moving the file.)
* Configure blocking of this file's transfer using:
* Email (e.g., Outlook).
* Cloud applications (e.g., Google Drive).
* Messaging apps (e.g., Microsoft Teams).
* **Effect:**
* Any attempt to send the price list file will be blocked, and the event will be recorded in the system logs.
### Summary
Trigger **"File Send"** provides comprehensive control over data transfers within the organization. With flexible configuration and broad channel support, the tool helps enforce security policies and minimizes the risk of unauthorized disclosure of sensitive data.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/file-sent.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.