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

# Assistant

ShieldLlama Assistant is Protege's enterprise copilot for searching, analyzing, and synthesizing information across your compliance environment.

It is designed to help legal, compliance, brand, and operations teams move faster without switching across multiple systems. Assistant can answer questions using the data already available in your Protege workspace, including document reviews, monitoring results, policies, claims, and related workflow context.

Use the pages in this section to understand:

* common enterprise use cases
* what data the assistant can access
* how to frame questions for better results

For customers evaluating deeper workflow automation or external agent integrations, see the enterprise [Integrations & API](/review/enterprise-features/integrations-and-api.md) guide.


---

# 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://gitbook.tryprotege.com/review/enterprise-features/assistant.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.