> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/features/settings/plan.md).

# Plan

In each section tab **Settings** there is a panel with basic information about the current subscription. This allows the user to check their plan at any time, see the usage of available limits, and go to subscription management.

Panel **My plan** shows the name of the current subscription, the usage of page and user limits, available features, and the plan start and expiration dates.

Button **Manage subscription** allows access to the payment portal, where you can manage the payment method, billing details, invoices, and plan cancellation.

Detailed information can be found in the sections [**Billing and licensing**](/en/system/billing-and-licensing.md) and [**Subscription cancellation**.](/en/features/settings/subscription/canceling-a-subscription.md)

<figure><img src="https://572977165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPbZABdmwpFq6bAJuwUC%2Fuploads%2FKdFOUim3o34KGujQFgAj%2Fimage.png?alt=media&amp;token=ced5ab80-8d69-442b-bf73-b8a0c71976fc" alt="Panel Mój plan z informacjami o subskrypcji, wykorzystanych limitach i przyciskiem Zarządzaj subskrypcją." width="234"><figcaption><p>Current subscription plan.</p></figcaption></figure>


---

# 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://bluurdoc.bluur.ai/en/features/settings/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.
