> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/account-and-team/billing-and-plans.md). # Billing and plans Manage your subscription, monitor seat usage, and understand plan tiers. #### Why use billing and plans * Track how seats are used and keep your plan matched to your team's needs * Change tiers or cancel with a clear picture of what happens to your content and access #### In this section * [**Check seat usage**](/account-and-team/billing-and-plans/how-to-check-seat-usage.md) - See how account, workspace, and journey-map seats are used and who occupies each. * [**Upgrade or downgrade**](/account-and-team/billing-and-plans/how-to-upgrade-or-downgrade.md) - Change plans and what happens to existing content and users. * [**Cancel subscription**](/account-and-team/billing-and-plans/how-to-cancel-subscription.md) - Cancel and understand what access is retained afterward. * [**Delete your account**](/account-and-team/billing-and-plans/how-to-delete-your-account.md) - Permanently remove your account and its data. This cannot be undone. * [**What's included in each plan**](/account-and-team/billing-and-plans/what-is-included-in-each-plan.md) - Reference for feature availability by plan tier. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdesk.smaply.app/account-and-team/billing-and-plans.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.