> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/security-and-governance/transfer-shield-dlp/manual-approvals.md). # Manual Approvals ## Introduction Transfer Shield can require a file to be manually reviewed before its transfer completes. Manual approval is configured as the action on a [**Content Rule Group**](/security-and-governance/transfer-shield-dlp/content-rule-groups.md). ## When approval is required When a file matches a Content Rule Group configured with **Require manual approval**, Couchdrop holds the transfer instead of completing it immediately. An approval task is then created on the **Tasks** page. ## Reviewing approval requests Approval tasks are assigned to the users or groups configured for the Content Rule Group. Assigned users can open the task in Couchdrop and approve or reject the file. Approvals cannot be completed from email. Email notifications can be used to notify assigned users that a file requires approval, but the approval itself must be completed from the Couchdrop UI. ## Files waiting for approval Files requiring approval remain held while the approval task is outstanding. They remain held until they are approved or deleted. --- # 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.couchdrop.io/security-and-governance/transfer-shield-dlp/manual-approvals.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.