> 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/chinese/guan-li-yu-she-zhi/settings/document-processing/module/show-report.md).

# 显示报告

### 概述

**显示报告**设置会在主导航菜单中添加一个**报告**入口。团队成员可以一键访问报告页面，查看文档处理相关报告。

此设置**默认处于禁用状态**。

### 此设置的作用

* **启用** — 侧边菜单中会显示**报告**项，链接到报告页面。用户可以打开该页面查看报告。
* **禁用** — 菜单中会移除**报告**项。

### 优势

* **深入了解**：直接从菜单访问文档处理相关报告。
* **快速访问**：需要时，一键即可打开报告。
* **界面整洁**：对于不使用报告的团队，可将其隐藏，让菜单保持简洁。

### 使用方法

1. 前往**设置**。
2. 选择**文档处理**。
3. 选择**模块**。
4. 打开**文档类型**部分。
5. 找到**显示报告**并开启开关。
6. 随后，组织的导航菜单中会显示一个**报告**入口。

### 何时使用此功能

* **监控与监督**：主管或管理员需要快速访问报告时。
* **定期审查**：报告属于团队日常工作流程的一部分时。
* 如果没有人需要报告，请**保持关闭**，让导航菜单保持简洁。


---

# 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/chinese/guan-li-yu-she-zhi/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.
