> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/project-management/workspaces/reference-workspaces/billing-and-plans.md). # Billing & Plans Billing in Motion is tied to the **workspace**, not the individual user. Each workspace has its own subscription plan, billing owner, and seat allocation. **Behavior** * **Workspace-level billing** → Each workspace manages its own subscription. If you belong to multiple workspaces, billing is handled separately for each. * **Seats** → The number of seats available depends on the subscription tier chosen for the workspace. Each member with Full Access (Owner, Admin, Member) occupies a seat. * **Billing owner** → Only the workspace Owner (or designated billing contact) can manage payment details, upgrade or downgrade plans, and purchase additional seats. * **Plan differences** → Features such as advanced permissions, integrations, or support options may vary by tier. **Why it matters**\ Billing and seat allocation define how many people can actively collaborate in your workspace. Choosing the right tier ensures you have enough capacity for your team’s size and access needs. --- # 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://www.usemotion.com/help/project-management/workspaces/reference-workspaces/billing-and-plans.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.