> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/cloud-licensing/engenius-cloud-licensing/cloud-dashboard-licenses.md). # Cloud Dashboard Licenses Organization–based and MSP Portal–based Licensing Cloud Dashboard Licenses operate under two licensing models — **Organization–based** and **MSP Portal–based** — providing flexibility for **shared resources** and **multi-organization management**. ## Licensing Models #### **Organization–based Licensing** * A license is assigned directly to **a specific organization,** providing **shared** resources (e.g., Shared AI Tokens). * These shared resources can be used by all devices within the organization that support the specific feature (e.g., Cloud-AI–enabled devices). #### **MSP** Portal**–based Licensing** * Designed for Managed Service Providers **(MSPs)** to centrally manage **multiple** organizations via the **MSP Portal**. * Streamlines operations and enhances multi-organization management capabilities. --- # 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://doc.engenius.ai/cloud-licensing/engenius-cloud-licensing/cloud-dashboard-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.