> 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/global-settings/subscription-plan.md).

# 订阅计划

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-d17de85db756434f7d5e9153eecb0df159a93a6c%2Fsubscriptions_overview.png?alt=media" alt="订阅计划"><figcaption><p>订阅计划页面</p></figcaption></figure>

**订阅计划**页面集中展示 DocBits 订阅的完整概览：订阅计划本身、为组织启用的应用和功能订阅，以及令牌使用情况。前往 **设置 → 组织与访问权限 → 订阅计划**即可打开此页面。

## 订阅计划

第一张卡片显示您的 DocBits 订阅信息，包括剩余天数以及开始和结束日期，并同时显示组织的实时统计数据：

| 卡片          | 说明               |
| ----------- | ---------------- |
| **DocBits** | 订阅剩余天数以及开始和结束日期。 |
| **用户**      | 您组织中的用户数量。       |
| **子组织**     | 子组织数量。           |
| **供应商**     | 供应商数量。           |

## 功能订阅

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-27614b7f3c88885a831a7a063ad6b00079d90e25%2Fsubscriptions_feature_subscriptions.png?alt=media" alt="功能订阅"><figcaption></figcaption></figure>

此部分列出每个 DocBits 应用和功能，以及它们是否已为您的组织启用。

| 列               | 说明                                                                                        |
| --------------- | ----------------------------------------------------------------------------------------- |
| **应用**          | DocBits 应用或功能（例如 AI Workforce、Operator、DocFlow、AI Search、BOD Ingestion、SQL BI Connector）。 |
| **订阅**          | 此应用订阅的计划。                                                                                 |
| **状态**          | **有效**、**正在取消**（在结束日期前保持有效，之后终止），或未订阅时显示 **无**。                                           |
| **开始日期 / 结束日期** | 订阅期限。                                                                                     |
| **剩余天数**        | 距离结束日期的剩余天数。                                                                              |
| **操作**          | 每个应用的操作菜单。                                                                                |

## 订阅用量

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-927989f4103535d4fee0a88b1f0a3b314c12f8be%2Fsubscriptions_usage.png?alt=media" alt="订阅用量"><figcaption></figcaption></figure>

监控所选期间内的令牌和工作流用量。使用 **选择**按钮选择日期范围。

| 列           | 说明                         |
| ----------- | -------------------------- |
| **类型**      | 用量类别：文档、工作流、高级工作流或 DocNet。 |
| **起始 / 结束** | 报告用量的期间。                   |
| **已使用令牌**   | 此期间消耗的令牌数。                 |
| **剩余令牌**    | 此期间剩余的令牌数。                 |


---

# 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/global-settings/subscription-plan.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.