> For the complete documentation index, see [llms.txt](https://docs.ovationvr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovationvr.com/ovation/creating-an-account/computer-licenses.md). # Licenses ### Individual Subscribers Individual subscribers receive 1 license and are not able to purchase more. ### Organization Subscribers Organization subscriptions start with 5 licenses. Organization licenses are based on a concurrent user licensing model. Each time a member of the Organization launches the Ovation application, they must sign in. While they are signed in, they are reserving a license. When they sign out, that license becomes available again. For example, a university with 15 licenses could have 15 students using Ovation simultaneously. If a 16th student attempted to launch Ovation and sign in, they may be prevented from doing so until a license becomes available. Ovation's flexible concurrent user licensing model means that organizations do not need to worry about how many headsets or computers they install Ovation on, how many "learners" they will have, or what their full-time equivalents (FTE) count is. Organizations can increase or decrease their license count by contacting . ## Organization Licenses Explanation {% embed url="" %} --- # 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://docs.ovationvr.com/ovation/creating-an-account/computer-licenses.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.