> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/getting-started/deployment-guides/file-security.md).
# File Security
### Custom Detections
Common use cases are covered with [Material's built in detections](/detections/detections-overview.md) (follow this guide to become familiar with those).
As you deploy or any time in your use of Material, you may also want to consider any policies unique to your organization's security strategy and create custom detections to reflect those. Learn how and when to [create custom detections](/detections/detections-overview/custom-detections.md) here.
**You don't need to create any custom detections to complete deployment**, however some common custom detections created at this time are:
| Query | Description |
| --------------------------------------------- | ---------------------------------------------------------------- |
| `category.any and shared.with_personal_email` | Users shared sensitive content with their personal email address |
| `category.any and shared.with_freemail` | Users shared sensitive content with a freemail account |
***
## File Search
## Step Three: Enable Remediation
Detections are enabled and creating issues immediately, but they're not yet responding. [Learn more about setting auto-response here](/working-with-issues/respond/configure-default-responses.md). In brief.
1. From the left navigation, click **Detections**.
2. Click **Filters,** then select **Entity Type** then **Files**.
3. Browse the existing File Detections.
4. Open the detection then set the default response as needed:
Detection default response
5. From this detection detail screen, you can also disable the Detection. At deployment, we recommend you leave them enabled and let them run.
Detection enabled
Default response descriptions are in [Configure Default Auto-Responses](/working-with-issues/respond/configure-default-responses.md).
{% hint style="success" %}
Auto-response is best practice, but if you need to revoke access manually for any reason — do this in the Explorer. [Learn more here](/workspace-protections/google-drive-security/bulk-remediate-and-revoke-access-to-files.md).
{% endhint %}
### Default Account Settings
---
# 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.material.security/getting-started/deployment-guides/file-security.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.
