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

# Protege Review Documentation

## What is Protege Review?

Protege Review is an AI-powered compliance review platform built for legal, compliance, and marketing teams. It scans your marketing content — documents, web pages, social media posts, images, and videos — against your organization's policies to identify legal risks, trademark issues, unsupported claims, and regulatory violations before they go live.

## Key Concepts

* **Document Review**: Submit content for AI analysis against your configured policy groups. Reviews can be triggered from within Google Docs, Microsoft Word, Figma, Photoshop, or directly from the Protege Review dashboard.
* **Policy Engine**: Define the compliance rules the AI evaluates against. Policies are organized into groups and applied based on document type, brand, and attributes. Manage attributes on the **Attributes** tab in Policy Engine.
* **Content Scanner**: Schedule recurring scans of your websites and social media accounts to continuously monitor published content for compliance issues.
* **Decision Store**: A centralized repository of approved claims, trademarks, and marketing language. Previously approved content is automatically recognized, reducing review time.
* **Brands & Attributes**: Associate content with specific brands and metadata (region, product, channel) so the right policies are applied to the right content.
* **Teach Your AI**: Provide feedback on AI results to improve detection accuracy over time. Approved feedback is used to retrain your organization's custom model.

## Getting Started

Install Protege Review in the tools your team already uses:

* [Document Editor Installation](/review/getting-started/document-editor-installation.md) — Google Workspace, Office 365, Figma, Adobe Creative Cloud
* [Task Manager Setup](/review/getting-started/task-manager-setup.md) — Asana, Jira, Smartsheets, Wrike
* [File Scanning Setup](/review/getting-started/file-scanning-setup.md) — Google Workspace, SharePoint, Frame.io

## Getting Support

1. **Email Support**: For any assistance, reach us at <support@tryprotege.com>. Our support team monitors this inbox closely and strives to respond promptly to all queries.
2. **Shared Slack Support (Enterprise)**: For enterprise clients, we can set up a shared Slack channel during onboarding for rapid collaboration with your team.

When reaching out for support, please provide as much detail as possible regarding the issue you're facing. This could include screenshots, error messages, or steps to reproduce the problem.

Our support team operates during Pacific time business hours. If you encounter an urgent issue outside of our regular support hours, please send an email marked urgent in the subject to <support@tryprotege.com>. We'll do our best to prioritize your request.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tryprotege.com/review/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.