> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/settings/subscription-management.md). # Subscription management Understand Agent seats, usage, usage limits and access requests for organisations where usage-based billing is enabled. Usage-based billing is enabled **per organisation** by Lleverage. Organisations that have not been enabled continue on their existing platform arrangement; the controls below only apply where usage-based billing is active. ### Agent seats and included usage An Agent seat gives a person direct Agent access. Seat assignment is separate from ordinary organisation membership, so people can belong to an organisation without automatically receiving Agent access. Paid Agent seats contribute to the organisation's included monthly usage according to its commercial terms. When a person needs Agent access, they can request a seat where that flow is enabled; organisation owners can approve seat requests from **Members** or **Plan & usage**. ### See current usage The usage meter in the main navigation shows the limit that is currently closest to being reached. * Organisation owners can see usage amounts. * Other members see percentages rather than monetary amounts. * Direct Agent usage by Lleverage staff can be tracked separately and is not billed to the customer. Organisation owners can use **Plan & usage** to see the current billing period, usage and available headroom, and to manage the controls available to their organisation. ![Plan & usage overview showing the current cycle, included usage and usage history.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-b705220dd75c619ec0b7d8f0268af647a6cf9bfd%2Fubb-usage-page.png?alt=media) > The screenshots on this page use a synthetic staging organisation. Names and example values are illustrative and do not represent customer data or Lleverage pricing. ### Usage limits Organisation owners can set monthly Agent-usage limits at several scopes: * organisation; * project; * member. If a member reaches a hard limit, **new Agent messages are paused** at that boundary. Background Workflows and scheduled runs keep running; a direct-Agent usage limit is not a global shutdown of recurring operational automation. Members can request a higher limit where the request flow is enabled, and owners can review those requests from **Members** or **Plan & usage**. ![Member-level Agent usage limits in the Members view.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-e850264dceb801b73e9769160d0a824d4e39630d%2Fubb-members-limits.png?alt=media) ![Project-level Agent usage limits in the Projects view.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-7c996330beeedfe90aa393ee14a85bfca4bba81a%2Fubb-project-limits.png?alt=media) Selecting a limit opens the editor for that scope. Changes only take effect when they are saved. ![Usage-limit editor for the selected scope.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-02b260af885720833637bfd6b6cfaf34d917ede5%2Fubb-limit-editor.png?alt=media) ### Additional usage An organisation can have additional usage bundles or adjusted limits as part of its commercial setup. Use the controls available in **Plan & usage** or work with your Lleverage contact when the organisation needs more headroom. ### Availability Usage-based billing is live, but activation is controlled per organisation. If you do not see the usage meter, **Plan & usage**, Agent-seat requests or usage-limit settings described here, usage-based billing has not been enabled for your organisation yet. --- # 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.lleverage.ai/administer-and-govern/control/settings/subscription-management.md?ask=&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.