> 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/policy-engine/viewing.md).

# Viewing

**Viewing Policies, Policy Groups, and Evaluation Types**

1. **Access the Dashboard**: Log in to your Protege account via the dashboard at [app.t](https://app.protegecounsel.ai/)[ryprotege.com](https://app.tryprotege.com).
2. **Click on the "Policy Engine" Tab**: Locate and click on the "Policy Engine" tab in the navigation menu. This will take you to the section where all policies and policy groups are managed.
3. **Review Policy Groups**: Once in the Policy Engine section, you'll find a list of Policy Groups displayed. Each Policy Group represents a collection of related policies bundled together for content evaluation.
4. **Explore Policy Details**: Within each Policy Group, you'll see the individual policies it contains. Click on any specific policy to expand it and view detailed steps outlining the procedures and criteria involved in implementing that particular policy.
5. **View Document Evaluations**: Each type of Document that you set for review in Protege AI can be assigned different Policy Groups to be conducted.


---

# 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/review-tool-concepts/document-review/policy-engine/viewing.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.