> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/shade-academy/shade-academy-zh/guan-li-yu-an-quan/billing.md).

# 计费

账单按工作区级别管理，只有工作区所有者可以查看和管理账单。定价很简单：你需要根据工作区已购买的席位数量和存储空间付费。你可以查看我们的价格方案 [这里](https://shade.inc/pricing)。席位和存储的增加会立即生效，并按账单周期剩余时间按比例计费。席位和存储的减少会在下一个续费周期生效。

我们对账单的查看和管理分布在应用中的两个页面上。

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FlIfNaYBPK7IsZyWKQmuc%2FBilling.gif?alt=media&#x26;token=3a9c2ef1-6aba-4122-bb74-1d848970da35" alt=""><figcaption></figcaption></figure>

## 使用情况

你的工作区使用情况可在“设置/使用情况”中找到，工作区管理员和工作区所有者均可查看。此页面概览了你的工作区如何使用存储、席位和访客。

要释放空间，请点击 **释放存储空间** 存储卡上的按钮并选择一个驱动器以打开文件管理器。文件管理器会列出该驱动器中的每个文件，允许你按大小或上传日期进行搜索、筛选和排序，并允许你选择文件并批量删除。

## 计费

你的工作区账单可在“设置/账单”中找到。此页面仅对工作区所有者可见，并包含：

* **方案详情：** 你当前的方案和账单周期，以及更改方案的选项。
* **使用情况：** 你的席位和存储，以及 **管理席位** 和 **管理存储** 用于增加或减少。
* **付款与发票：** 你的付款方式、发票收件人和过往发票。

## 常见问题

### 如何降低我的账单？

你可以将工作区成员移为他们需要访问的驱动器上的访客。请注意，即使访客拥有完全访问权限，也无法挂载这些驱动器或访问其元数据。批量购买存储空间是降低存储成本的另一种方式。你还可以通过考虑使用代理工作流来降低存储成本 [这里](https://academy.shade.inc/guides)。在代理工作流中，你将原始文件保留在磁盘或 NAS 上，并将代理文件同步到已挂载的 Shade 驱动器。


---

# 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://academy.shade.inc/shade-academy/shade-academy-zh/guan-li-yu-an-quan/billing.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.
