> 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/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md).
# Google Drive playbooks for internal collaborator sharing
To mitigate the risk associated with internal sharing in Google Drive, you can define automated workflows for these use cases:
* [Auto-expire cross-team collaboration](#auto-expire-cross-team-collaboration)
* [Remove cross-team collaboration](#remove-cross-team-collaboration)
* [Remove internal collaborators on-demand](#remove-internal-collaborators-on-demand)
* [Remove internal and external collaborators on-demand](#remove-internal-and-external-collaborators-on-demand)
* [Remove org-wide sharing link on-demand](#remove-org-wide-shared-link-on-demand)
## Auto-expire cross-team collaboration
When someone shares a file in Google Drive with other team members, the actor is notified by email, and after a waiting period, any collaborators who are not in a specific group are removed.
{% hint style="info" %}
When an asset exists in a parent folder, collaborator access is removed from all assets in the folder.
{% endhint %}
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Google Drive app, and select the **Auto-expire cross-team collaboration** playbook.
3. Give an action name.
4. Under the **Change user access** event, define the relevant conditions:
* The `Get actor email` condition is in a specific group.
* The `Added collaborators` condition contains at least one collaborator from a specific group.
5. Add any relevant conditions.
6. Customize the email message to send to the actor about internally sharing a Google Drive file with a collaborator.
7. Customize the wait action (number of days or weeks to wait).
8. Customize the array filter step for `Added collaborators` that are **not** in a specific group within your organization. These collaborators are removed from the Google Drive file.
## Remove cross-team collaboration
When someone shares a file in Google Drive with other team members, the actor is notified by email, and any collaborators who are not in a specific group are removed.
{% hint style="info" %}
When an asset exists in a parent folder, collaborator access is removed from all assets in the folder.
{% endhint %}
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Google Drive app, and select the **Remove cross-team collaboration** playbook.
3. Give an action name.
4. Under the **Change user access** event, define the relevant conditions:
* The `Get actor email` condition is in a specific group
* The `Added collaborators` condition contains at least one that's in a specific group
5. Add any relevant conditions.
6. Customize the email message to send to the actor about internally sharing a Google Drive file with a collaborator.
7. Customize the array filter step for `Added collaborators` that are **not** in a specific group within your organization. These collaborators are removed from the Google Drive file.
## Remove internal collaborators on-demand
You can trigger an inventory action to remove all internal collaborators from My Drive assets on-demand.
When assets are shared with users from your organization, there's a risk of breaching "ethical walls" between departments. After removing internal access permissions, asset owners still have access to their assets.
{% hint style="success" %}
You can customize [inventory actions ](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md)to meet your organization's requirements. When you trigger the inventory action, select the relevant workflow you created.
{% endhint %}
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to Internal collaborator sharing, and select the **Remove internal collaborators on-demand** playbook for Google Drive.
3. Save the workflow with a new name.
4. Customize the **Remove collaborator** action, especially the error handling.
5. When you trigger the inventory action, select the relevant workflow you created.
## Remove internal and external collaborators on-demand
You can trigger an inventory action to remove all internal and external collaborators from My Drive assets on-demand.
When assets are shared with users from your organization, there's a risk of breaching "ethical walls" between departments. Sharing assets with users outside your organization increases the risk of data exfiltration.
After removing both internal and external access permissions, asset owners still have access to their assets.
{% hint style="success" %}
You can customize [inventory actions ](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md)to meet your organization's requirements. When you trigger the inventory action, select the relevant workflow you created.
{% endhint %}
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to Internal collaborator sharing, and select the **Remove internal and external collaborators on-demand** playbook for Google Drive.
3. Save the workflow with a new name.
4. Customize the **Remove collaborator** action, especially the error handling.
5. When you trigger the inventory action, select the relevant workflow you created.
## Remove org-wide sharing link on-demand
You can trigger an inventory action to remove org-wide shared links from Google Drive assets on-demand.
{% hint style="success" %}
You can customize [inventory actions ](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md)to meet your organization's requirements. When you trigger the inventory action, select the relevant workflow you created.
{% endhint %}
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to Internal collaborator sharing, and select the **Remove org-wide shared link on-demand** playbook for Google Drive.
3. Verify that the link type to remove is Organization.
4. Add any actions, such as **Notify by Email** or in **Slack**.
5. Save the workflow with a new name.
6. When you trigger the inventory action, select the relevant workflow you created.
---
# 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/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-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.
