> 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/identity-risk-management/google-drive-playbooks-for-identity-risk-management.md).
# Google Drive playbooks for identity risk management
To mitigate risky identities in Google Drive, you can leverage DoControl's automated playbooks for these use cases:
* [Monitor and remediate watchlist users who share with personal emails](#monitor-and-remediate-watchlist-users-who-share-with-personal-emails)
* [Monitor downloads by watchlist users](#monitor-downloads-by-watchlist-users)
## Monitor and remediate watchlist users who share with personal emails
When a watchlist user shares Google files with his/her own personal email, their manager is automatically notified and any personal emails are removed from file sharing permissions.
1. Select **Workflows > Playbooks**.
2. Filter the playbooks according to the **Identity risk management** category and **Google Drive** app.
3. Select the **Monitor and remediate watchlist users who share with personal emails** playbook.
4. Give the workflow a description.
5. Under the **Change user access** event, the relevant conditions are already pre-populated:
* **Has added collaborators** is True
* **Actor email** is in watchlist
* **At least one collaborator** is in the default personal email list
6. If necessary, customize the email notification that is sent to the actor's manager.
7. Save the workflow with a new name.
## Monitor downloads by watchlist users
When a watchlist user downloads a Google Drive file, the file is automatically scanned to check for sensitive content (PII). If PII is found, the SecOps team is notified.
1. Select **Workflows > Playbooks**.
2. Filter the playbooks according to the **Identity risk management** category and **Google Drive** app.
3. Select the **Monitor downloads by watchlist users** playbook.
4. Give the workflow a description.
5. Under the **Download** event, the relevant conditions are already pre-populated:\
**Get actor email** is in watchlist
6. In the **PII scan** step, select the PII labels you want to search for in the downloaded file.
7. In the **Conditional** step, verify the probability of finding matches for your PII terms.
8. If necessary, customize the Slack notification that is sent to the SecOps team.
---
# 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/identity-risk-management/google-drive-playbooks-for-identity-risk-management.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.
