> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/document-processing/module/show-report.md).

# Show Report

### Overview

The **Show Report** setting adds a **Report** entry to the main navigation menu. It gives your team one-click access to the reporting page, where you can review reporting on your document processing.

This setting is **disabled by default**.

### What Does It Do?

* **Enabled** — A **Report** item appears in the side menu, linking to the reporting page. Users can open it to view the report.
* **Disabled** — The Report item is removed from the menu.

### Benefits

* **Insight**: Reach reporting on your document processing directly from the menu.
* **Quick access**: The report is one click away when it is needed.
* **Tidy interface**: Keep the menu focused by hiding the report for teams that don’t use it.

### How to Use

1. Go to **Settings**.
2. Select **Document Processing**.
3. Select **Module**.
4. Open the **Document Type** section.
5. Find **Show Report** and switch the toggle on.
6. A **Report** entry then appears in the navigation menu for the organization.

### When to Use This Feature

* **Monitoring and oversight**: When supervisors or admins want quick access to reporting.
* **Regular reviews**: When the report is part of your team’s routine.
* **Leave it off** if no one needs the report, to keep the navigation focused.


---

# 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.docbits.com/administration-and-setup/settings/document-processing/module/show-report.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.