> 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/personal-account-sharing/okta-playbooks-for-personal-account-sharing.md).
# Okta playbooks for personal account sharing
To mitigate the risk associated with personal account sharing for a deactivated Okta user, you can define automated workflows for these use cases:
## Remediate terminated employee's personal email access to Google Drive
When a employee is terminated by deactivating their Okta account, DoControl automatically runs an API to remediate any Google files that were shared with the employee's personal email account. If the remediation action doesn't complete successfully, the Security team is notified, and the remediation is run again after a defined time interval.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Okta app, and select the **Remediate terminated employee's personal email access to Google Drive** playbook.
3. Give an action name.
4. Customize the **User lifecycle deactivate** Okta event, for when an employee has been terminated.
5. Customize the **Get user metadata** step to retrieve the terminated employee's personal email from the HRIS app, such as HiBob or Workday.
6. Customize the **DoControl API** step to run a bulk remediation to remove the terminated employee's personal email from all Google assets shared with him.
7. Customize the **Conditional** step that the remediation assessment process started:
* If true, end the workflow with success.
* If false, customize the **Notify by email** step to email the Security team that the remediation could not be completed, and will be run again in 60 minutes. \
Customize the **Wait** step with the length of time to wait before running the remediation again.
---
# 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/personal-account-sharing/okta-playbooks-for-personal-account-sharing.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.
