> 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/saas-data-monitoring/content-scans.md).
# Content scans
When managing large volumes of data and communication, it can be helpful to scan files for sensitive content, such as personally identifiable information (PII) or financial details. Detecting outdated information or inappropriate language enables your organization to comply with regulatory standards.
You can run a content scan to locate specific words or phrases in:
* [Google Drive](/docontrol-user-guide/saas-data-monitoring/content-scans/google-drive-scan.md) - Specific My Drives in your organization's Google Workspace, or
* [Slack Enterprise ](/docontrol-user-guide/saas-data-monitoring/content-scans/slack-enterprise-scan.md)- All conversations from any 6-month time range
{% hint style="warning" %}
* You need **Admin** permission in DoControl to create, download or delete a content scan.
* If your organization is large, DoControl recommends to run several content scans, and limit each one to 1,000 My Drives.
{% endhint %}
A list of your organization's content scans with links to all assets containing search terms
## Use cases
Scanning your Slack workspace for specific content provides critical visibility into potential data security risks and policy violations that might otherwise go undetected. A content scan can help you to:
* **Detect inadvertent or malicious sharing of sensitive information** - Identify any personally identifiable information (PII), credentials, or intellectual property that is shared in Slack conversations.
* **Detect insider threats or compliance breaches** - Enforce regulation compliance, such as GDPR requests to forget the names or emails of individuals.
* **Respond faster and mitigate potential damage -** DoControl allows you to scan large volumes of data across all Slack Enterprise conversations, enabling early detection.
{% hint style="info" %}
DoControl doesn't process the content of your Google Drive files. We leverage search terms across Google APIs to find the information you need.
{% endhint %}
---
# 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/saas-data-monitoring/content-scans.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.
