> 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/docontrol-playbooks-for-identity-risk-management.md).
# DoControl playbooks for identity risk management
To mitigate risky identities in Google Drive, you can leverage DoControl's automated playbooks for these use cases:
* [Notify on identity risk spike](#notify-on-identity-risk-spike)
* [Notify on identity risk spike for a terminated user](#notify-on-identity-risk-spike-for-a-terminated-user)
## Notify on identity risk spike
When a user's risk score increases and the user becomes risky, automatically notify your security team.
1. Select **Workflows > Playbooks**.
2. Filter the playbooks according to the **Identity risk management** category and the **DoControl** app.
3. Select the **Notify on identity risk spike** playbook.
4. Give the workflow a description.
5. Under the **Identity risk score changed** event, the risk spike values are already pre-populated:
* **Identity risk score difference** is greater than 30
* **New identity risk score** is greater than 70
6. If necessary, customize the identity risk spike values.
7. Customize the **Slack** message that is sent to your SecOps team notifying them about the user's risk score spike.
## Notify on identity risk spike for a terminated user
When a terminated user's risk score increases, automatically notify your security team.
1. Select **Workflows > Playbooks**.
2. Filter the playbooks according to the **Identity risk management** category and the **DoControl** app.
3. Select the **Notify on identity risk spike for terminated user** playbook.
4. Give the workflow a description.
5. Under the **Identity risk score changed** event, the conditions are already pre-populated:
* User's employment status is terminated
* **New identity risk score** is greater than 40
6. If necessary, customize the identity risk spike value.
7. Customize the **Slack** message that is sent to your SecOps team notifying them that a terminated user's risk score increased significantly.
---
# 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/docontrol-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.
