> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/6.-resources-documentation-and-terms/faq/team-account-management/will-my-team-stop-functioning-if-i-dont-renew-the-subscription-after-it-expires.md).

# Will My Team Stop Functioning If I Don’t Renew the Subscription After It Expires?

The Cregis team plan provides a 7-day grace period after expiration. If the renewal is not completed within 7 days, the upgraded services will be terminated. If you have used capacity expansion services, the related services will no longer function properly after expiration. For example, if you created two multi-signature wallets during the upgrade, the use of these wallets will be restricted after expiration. To avoid affecting your operations, please be sure to renew as soon as possible before the expiration date.

To avoid disruptions to your daily operations caused by forgetting to renew, we recommend that you enable the [auto-renewal service](/2.-transaction-and-account/images-and-media/manage-your-pricing-plan.md#auto-renewal).


---

# 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://support.cregis.com/6.-resources-documentation-and-terms/faq/team-account-management/will-my-team-stop-functioning-if-i-dont-renew-the-subscription-after-it-expires.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.