> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/encryption-key-sharing/onedrive-playbooks-for-ransomware-upload.md).

# OneDrive playbooks for ransomware upload

To notify about uploading ransomware to OneDrive, you can customize an automated workflow to notify your security team whenever ransomware files are uploaded to OneDrive.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to **OneDrive** app, and select the **Notify on uploading ransomware** playbook.
3. Under the **Added to secure link** event, the condition is already populated:\
   File extension is ransomware.

<div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F5owI5nOl5MHgBqTWbKLl%2FNotify%20on%20sharing%20ransomware.png?alt=media&amp;token=153eb937-eff1-4359-a3a3-0cebc779a84a" alt=""><figcaption></figcaption></figure></div>

4. Add any relevant conditions.
5. Customize the **Notify by email** action to notify your security team that suspected ransomware was uploaded to OneDrive.


---

# 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://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/encryption-key-sharing/onedrive-playbooks-for-ransomware-upload.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.