> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/documentation/zh/zhang-hu-yu-ji-fei/plans/cancelling-a-plan.md).

# 订阅取消

{% hint style="warning" %}
在取消之前，请联系我们的 [支持团队](#cancel-plan-button-missing) — 我们也许能够解决该问题。
{% endhint %}

如果你的当前订阅显示有一个 **取消方案** 按钮，请按以下步骤操作：

1. 前往 **组织设置** — 点击侧边栏底部的设置图标，然后点击 **\[组织名称] 设置**.
2. 点击 **计费**.
3. 点击取消订阅

### **缺少“取消方案”按钮**

如果你已经点击进入 **组织设置** → **计费** 并且没有看到 **“取消订阅”按钮**, [请联系 GitBook 支持](#cancel-plan-button-missing)。不要重复自助流程。

支持团队可以查看你的订阅，并在适当情况下代表你取消订阅或安排取消。

请在请求中包含以下内容：

* 你的组织名称。
* 你 GitBook 账户上的电子邮件地址。
* 你当前的方案。
* 你的下次续费或预期扣费日期。
* 你最近的一张发票或收据编号（如果有）。
* 确认 **取消订阅** 未在 GitBook Billing 或 Stripe 门户中显示。
* 你是否希望在当前计费周期结束时取消。

{% hint style="info" %}
你的方案会一直保持有效，直到计费周期结束。之后将不会续费。
{% endhint %}

### **当试用结束、付款失败或订阅失效时**

已结束的试用、付款失败或失效的订阅与主动取消不同——它会立即限制协作，而不是在计费周期结束时才限制。

如果协作受限，成员将失去对组织及其内容的访问权限。主管理员仍保留管理组织的访问权限。

要恢复访问权限，主管理员可以：

1. 打开组织的计费设置，续费可用方案或开始新的订阅。恢复订阅会恢复所有成员的访问权限。
2. 如果付款失败，请在计费流程中更新付款信息，然后完成续费。
3. 如果新方案的成员席位更少，请在选择方案之前移除不再需要访问权限的成员。移除成员不会删除他们之前贡献的内容。

### **续费已取消的方案**

如果你已取消方案且计费周期尚未结束，你可以续费。点击 **续费方案**，然后在下一页再次点击以确认。你的订阅将自动续费。

如果你的计费周期已经结束，你可以购买新方案。


---

# 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://gitbook.com/docs/documentation/zh/zhang-hu-yu-ji-fei/plans/cancelling-a-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.