> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/manage-your-organization-and-workspace/manage-your-organization/subscriptions-and-usage.md).

# Subscriptions and usage

Use this screen to manage your organization plan, billing, and purchases, and to monitor usage across your organization and workspaces.

### Manage subscriptions

{% hint style="info" %}
Only users with the organization role **Admin** or **Billing** can change the subscription or make purchases.
{% endhint %}

In the **Manage subscriptions** section you can:

* See which plan is active. The current plan is marked on its card.
* Switch between **Monthly** and **Annual** billing.
* Compare **Free**, **Team**, and **Business** side by side.

The available plans include:

* **Free** for individuals getting started
* **Team** for small teams building and sharing apps
* **Business** for teams that need advanced security and control

Use the plan cards to compare included features, limits, and pricing.

### Track usage

In the **Track usage** section you can:

* Switch between **Organization** and **Workspace** usage.
* Check when usage data was last updated.
* Review current usage against the included limit for each metric.

In **Organization** usage you can track:

* **Storage**
* **Records**
* **API calls**
* **Documents generated**
* **Linked emails**

In **Workspace** usage you can:

* Search for a workspace
* Compare usage across workspaces in one table
* Review **Storage**, **Records**, **API calls**, **Documents generated**, **Sent emails**, and **Linked emails** for each workspace

This gives you one place to manage billing and monitor usage for the organization and its workspaces.


---

# 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://docs.ninox.com/builder-hub/manage-your-organization-and-workspace/manage-your-organization/subscriptions-and-usage.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.