> 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/documents-expiry.md).

# 文档过期时间

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-ea9216f517d84d5843a34af54f9315ebfdac197c%2Fdocument_expiry_settings_overview.png?alt=media" alt="文档过期时间设置"><figcaption><p>文档过期时间设置</p></figcaption></figure>

在 **Document Processing → Documents Expiry** 下，您可以设置 DocBits 在自动删除文档前保留文档的时长。这有助于管理存储空间、执行数据保留策略，并遵守关于文档存储时长的法律或组织规定。

以下两项设置用于控制自动删除：

| 设置                                 | 控制内容                        |
| ---------------------------------- | --------------------------- |
| **Delete document after**          | 任何已处理文档在自动删除前的保留时长。         |
| **Delete finished document after** | 已完成（已完整处理并导出）文档在自动删除前的保留时长。 |

对于每项设置，您都可以从下拉菜单中选择一个时间段：

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-abc876f4c734d68b1e1a702d527666ea58318c52%2Fdocument_expiry_options.png?alt=media" alt="文档过期时间选项"><figcaption><p>可用的保留期限</p></figcaption></figure>

| 选项           | 含义                    |
| ------------ | --------------------- |
| **Default**  | 使用系统默认保留期限（不进行自定义覆盖）。 |
| **48 Hours** | 在处理 48 小时后删除。         |
| **1 Week**   | 一周后删除。                |
| **2 Weeks**  | 两周后删除。                |
| **4 Weeks**  | 四周后删除。                |

这两项设置可确保文档不会在系统中保留超过必要的时间，避免占用不必要的存储空间，并让文档工作流保持整洁。对于必须遵守特定文档保留法规要求的组织，这些设置尤为重要。


---

# 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/documents-expiry.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.