> 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, Evaluations, and Attributes**

1. **Access the Dashboard**: Log in to your Protege Review account via the dashboard at [app.tryprotege.com](https://app.tryprotege.com).
2. **Open Policy Engine**: Locate and click **Policy Engine** in the navigation menu. This is where policies, policy groups, document evaluations, and attributes are managed.
3. **Review Policy Groups**: On the **Policies** tab, you'll find a list of Policy Groups. 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**: Open the **Document Evaluations** tab. Each document type you set for review can be assigned different Policy Groups.
6. **Manage Attributes**: Open the **Attributes** tab to create attribute categories and link databases used in policy steps. Attributes are configured here, not in 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.tryprotege.com/review/review-tool-concepts/document-review/policy-engine/viewing.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.