> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/review-tool-concepts/document-review.md).

# Document Review

Document Reviews in Protege Review allow users to specify the parameters for analyzing content based on specific document policy configurations. Each document review type can comprise multiple policy groups, providing comprehensive assessment criteria tailored to different document types or contexts.

**Overview:**

Document Reviews serve as customizable frameworks for evaluating content, enabling users to define the scope and criteria for analysis according to their requirements. By assigning policy groups to document review types, users can ensure a thorough examination of content for legal risks and compliance considerations.\
\
**Example Document Review Types:**

1. **Marketing Material Review**:
   * Policy Groups:
     * Core SaaS Policies
     * Marketing Compliance Guidelines
     * Branding and Messaging Standards
2. **Document Request Review**:
   * Policy Groups:
     * Sender Identification
     * Requirements Policy
     * Case Number Identification
3. **Social Media Review**
   * Policy Groups:
     * Claims Policy
     * Trademark Policy
     * Sponsorship Disclosure Policy

**Managing Document Reviews:**

Document reviews can be managed and different Policy Groups attached as needed. To make a change, users should write into support to create Policies, adjust Policy Groups, or create new Document Reviews to accommodate evolving company requirements. The support email is <support@tryprotege.com>, or you can use your shared external channel with the Protege team.

Enterprise customers who want to integrate Protege into their own systems or agent workflows should start with the enterprise integration guide:

{% content-ref url="/pages/kPBUSnugF2uhvh9BvOQw" %}
[Integrations & API](https://docs.tryprotege.com/review/enterprise-features/integrations-and-api.md)
{% endcontent-ref %}

\
If you have any questions or need assistance with setting up or managing document reviews, please don't hesitate to reach out to our support team for guidance. We're here to help you optimize your content review workflows and ensure compliance with ease.


---

# 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.tryprotege.com/review/review-tool-concepts/document-review.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.
