> 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.md).

# Internal collaborator sharing

**SaaS security problem**

Internal collaboration is considered standard practice. By working together in cross-department teams, organizations benefit from collaborative product development, increased sales through cross-selling, and sharing of best practices that reduce costs.

However, cross-team collaboration significantly increases the volume of sensitive data vulnerable to exfiltration. When excess permission privileges are granted to cross-team users within your organization, then unauthorized access to sensitive data poses a real risk.

In addition, access often remains long after it is needed. Files stored in SaaS applications retain their sharing permissions indefinitely. This is not only bad business practice, but significantly increases the volume of sensitive data vulnerable to exfiltration when insider threats or weak access controls prevail.&#x20;

**DoControl solution**

DoControl allows you to limit internal sharing by approaching SaaS data permissioning from a position of least privilege. You can regularly review and update permissions, and remove access when assets are no longer needed by the parties with whom they were shared. This helps to minimize data overexposure, and mitigate the risk of data loss.

To protect data integrity and maintain a secure environment for collaboration within SaaS platforms, DoControl leverages these tools to automatically monitor, mitigate, and remediate the risks associated with internal collaborator sharing:

* [Inventory](#inventory-of-internal-collaborators)
* [Playbooks](#playbooks-for-internal-collaborator-sharing)

## Who's an internal collaborator?

An internal collaborator is anyone working for your organization as a salaried or freelance employee with access to your organizational SaaS data.

## What's the risk?

Internal collaboration involves sharing confidential information across your organization's internal SaaS platforms. Weak access controls and legacy permission systems open the door for insider threat. Malicious actors with access to company assets can easily exfiltrate sensitive data, and cause significant damage to your organization.

## Inventory of internal collaborators

DoControl's rich inventory exposes internal collaborators for assets, by indicting the sharing status for each asset (internal or external). From the Assets page, you can:

* Filter assets per app for internal collaborators
* Remediate assets using [inventory actions](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md), such as change owner or remove collaborators

Filters for internally shared assets vary according to app:

<table><thead><tr><th width="194">SaaS app</th><th>Filter for internally shared assets</th></tr></thead><tbody><tr><td>Box</td><td><p>Sharing status includes:</p><ul><li>People in your company - Anyone in your organization with a Box account can access this asset</li><li>Internal</li></ul></td></tr><tr><td>GitHub</td><td><p>Visibility includes:</p><ul><li>Private</li><li>Internal</li><li>Private template</li></ul></td></tr><tr><td>Google Drive</td><td><p>Sharing status includes:</p><ul><li>Internal</li><li>Internal with link</li></ul></td></tr><tr><td>OneDrive</td><td><p>Click an icon that indicates the asset's sharing status: </p><ul><li>Organization assets <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FBfULuNVgx1o87Htrdo5T%2Forganization%20share%20icon.png?alt=media&amp;token=2371a0e5-1578-4b43-9333-5703665466d2" alt="" data-size="line"></li><li>Internal assets <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FwklgEfcWTAoFyFN8oUIE%2Finternal%20share%20icon.png?alt=media&amp;token=cc561cd8-7199-4e31-b8e2-6a5c41ac6a95" alt="" data-size="line"></li></ul></td></tr><tr><td>Salesforce</td><td>Sharing privacy includes Private</td></tr><tr><td>SharePoint</td><td><p></p><p>Click an icon that indicates the asset's sharing status: </p><ul><li>Organization assets <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FBfULuNVgx1o87Htrdo5T%2Forganization%20share%20icon.png?alt=media&amp;token=2371a0e5-1578-4b43-9333-5703665466d2" alt="" data-size="line"></li><li>Internal assets <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FwklgEfcWTAoFyFN8oUIE%2Finternal%20share%20icon.png?alt=media&amp;token=cc561cd8-7199-4e31-b8e2-6a5c41ac6a95" alt="" data-size="line"></li></ul></td></tr><tr><td>Slack</td><td>Channel type includes Private</td></tr><tr><td>Teams</td><td><p></p><p>Click an icon that indicates the asset's sharing status: </p><ul><li>Organization assets <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FBfULuNVgx1o87Htrdo5T%2Forganization%20share%20icon.png?alt=media&amp;token=2371a0e5-1578-4b43-9333-5703665466d2" alt="" data-size="line"></li><li>Internal assets <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FwklgEfcWTAoFyFN8oUIE%2Finternal%20share%20icon.png?alt=media&amp;token=cc561cd8-7199-4e31-b8e2-6a5c41ac6a95" alt="" data-size="line"></li></ul></td></tr><tr><td>Zoom</td><td><p></p><p>Sharing status includes Internal</p></td></tr></tbody></table>

#### To filter and remediate assets that are shared internally:

1. In the Assets page, select the relevant SaaS app.
2. Filter for a **sharing status** that includes **Internal**, or any other internal sharing filter, such as **Internal with link**.\
   For example: Filter for Google Drive assets within a specific department that are shared with an internal link.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FaB7Y9r22DDuv4vrsnuY2%2Finternal%20sharing%20filters.png?alt=media&amp;token=d0098e28-1ae5-4e8b-afa1-c083e3f34166" alt=""><figcaption></figcaption></figure>
3. Select one of more assets.
4. Click **Remediate > Inventory actions**, and select the relevant inventory action:
   * Remove internal collaborators&#x20;
   * Remove specific collaborators
   * Remove all collaborators
   * Change owner

{% hint style="info" %}
Google Drive assets: Inventory actions are supported only for Google Drive assets shared externally or publicly, or assets located in personal drives (My Drive).
{% endhint %}

## Playbooks for internal collaborator sharing

To address the use cases of internal collaborator sharing across various SaaS apps, you can define automated workflows with DoControl's out-of-the-box playbooks. These playbooks will:

* Automatically remove collaborators who are not in a specific team in your organization
* Remove organization links from shared OneDrive and SharePoint assets

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F1C8CMwjXWZurgffuYKwk%2Finternal%20collab%20sharing%20PBs.png?alt=media&amp;token=dc1bb8b2-3122-461a-82a2-1af37ef63b19" alt=""><figcaption><p>Select a predefined DoControl playbook to remediate internal collaborator sharing</p></figcaption></figure>

<table><thead><tr><th width="312">Playbook name</th><th width="169.33333333333331">SaaS app</th><th>Playbook description</th></tr></thead><tbody><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md#remove-cross-team-collaboration">Remove cross-team collaboration</a></td><td>Google Drive</td><td>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.</td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md#auto-expire-cross-team-collaboration">Auto-expire cross-team collaboration</a></td><td>Google Drive</td><td>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.</td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md#remove-internal-collaborators-on-demand">Remove internal collaborators on-demand</a></td><td>Google Drive</td><td>When a user triggers a DoControl inventory action to remove internal collaborators, all internal access permissions are automatically removed from selected My Drive assets. </td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md#remove-internal-and-external-collaborators-on-demand">Remove internal and external collaborators on-demand</a></td><td>Google Drive</td><td>When a user triggers a DoControl inventory action to remove internal and external collaborators, all internal and external access permissions are automatically removed from selected My Drive assets. </td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md#remove-org-wide-shared-link-on-demand">Remove org-wide sharing link on-demand</a></td><td>Google Drive</td><td>When a user triggers a DoControl inventory action to remove the company sharing link, the link is automatically removed from selected Google Drive assets.</td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/onedrive-playbooks-for-internal-collaborator-sharing.md#remove-organization-link-on-demand">Remove organization link on-demand</a></td><td>OneDrive</td><td>When a user triggers a DoControl inventory action to remove an organization link in OneDrive, the link is automatically removed.</td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/sharepoint-playbooks-for-internal-collaborator-sharing.md#remediate-ethical-wall-violations">Remediate ethical wall violations</a></td><td>SharePoint</td><td>When a user shares a sensitive file containing PII (personally identifiable information) with a user outside their SharePoint group, external collaborators are removed.</td></tr><tr><td><a href="/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/sharepoint-playbooks-for-internal-collaborator-sharing.md#remove-organization-link-on-demand">Remove organization link on-demand</a></td><td>SharePoint</td><td>When a user triggers a DoControl inventory action to remove an organization link in SharePoint, the link is automatically removed.</td></tr></tbody></table>


---

# 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.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.
