> 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/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/dashboard/document-merging.md).

# 文档合并

合并文档

## 概述

文档合并功能允许您将多个文档合并为一个文档。

首先，选择要合并的文档。您可以勾选文档旁边的复选框来选择。选好文档后，点击带有三个点的图标。

随后会显示一个菜单，请选择底部的“Merge”（合并）选项。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-6e7678a3ece762abd2d22dbb1338a3d66db02a05%2Fdocument-merging%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/TV2KGh2Q38KsO5Zi-O-GKp5v42Lam4WSj8I8Ia6KjVj2c4X6vce2nFt7yJYicRWmDwKOHZDxrAsfEYtMpN-9UD2mpJ9Sfs4ueb1AYAOjKngY25JKaeEBPzUwcbrylwQ4jj_v-jkGZYLey9p9i0LfL-I" alt=""><figcaption></figcaption></figure>

文档合并是文档管理系统中的一项重要功能，可帮助用户将多个文档合并为一个文档。文档合并有以下用途：

* \*\*整理相关文档：\*\*将多个文档合并为一个文档，便于用户将相关信息或文件集中整理和保存。这有助于提高文档管理与访问效率。
* \*\*创建报告或摘要：\*\*合并多个文档，可以汇总来自不同来源或文档的数据与信息，从而创建报告或摘要。用户无需手动复制粘贴信息，即可生成完整的报告或演示文稿。
* \*\*归档文档：\*\*当某个文档存在多个版本，或需要汇总特定时间段内的文档时，合并文档有助于确保归档方式一致并优化存储空间。
* \*\*优化工作流：\*\*文档合并可以作为自动化工作流的一部分，在满足特定条件后自动合并文档。例如，这可用于审批流程，或合同和报告的创建。

## 文档合并示例：

* \*\*合并发票：\*\*企业需要汇总某个月的所有发票，以便进行会计处理。各张发票分别作为独立文档上传，然后合并为一份汇总文档。
* \*\*合并审批表：\*\*申请审批工作流要求先合并多个表单，再转交管理层。相关各方完成并提交表单后，系统会自动将其合并。
* \*\*创建年度报告：\*\*公司内的多个部门共同编制一份完整的年度报告。每个部门将自己负责的章节整理为单独的文档，然后合并这些文档，形成最终的年度报告。

通过合并文档，组织可以简化文档管理流程、改善协作并提高效率。


---

# 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/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/dashboard/document-merging.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.
