> 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/engenius-licensing-ordering-claiming-and-assigning.md).
# EnGenius licensing - Ordering, Claiming, & Assigning
{% stepper %}
{% step %}
## Customer Purchases EnGenius License
### **License Order and License Key**
Partners purchase EnGenius Cloud licenses just like purchasing other hardware devices from EnGenius, except "**delivery email list**" information is required for the License Key to be mailed to. Once license P.O. is completed, the EnGenius license server will generate License Keys based on the order content and email to the recipients listed in the "delivery email list".
* A purchase order (P.O.) contains **multiple order lines**.
{% hint style="info" %}
One license model corresponds to one order line.
{% endhint %}
* One order line will generate **one license key.**
* An Email list is mandatory in the License purchase order.
* License key information (PDF) will be sent to the "delivery email list".
Lead time for license purchase order (P.O) should be within a few days. Suggest placing the license order whenever it's needed for deployment.
### License Key vs. License
* **License key** presents a group of Licenses (i.e. a quantity of 4 for AP-1YR-LIC)
* ***One order line*** from a PO (Purchase order) will generate *one license key*
* When inserting ***License Key*** into EnGenius cloud system, the ***License*** is **unzipped** automatically. (there would be 4 licenses of AP-1YR-LIC extracted from one license key in this case).
### License Key document (PDF attached in email)
* License key document (PDF) will be attached with the **license notification email.**
* PDF contains the purchased license model, quantity, validity period and its corresponding ***License Key*****.**
{% endstep %}
{% step %}
## Customer claims the license key within the Organization or the MSP Portal
### **Per-Device Licensing model or Organization-based Licensing model Claim**
You will have the ability to claim licenses in your organization. The licenses claimed in an organization cannot be unclaimed so make sure you are adding it to the correct organization. (However, licenses can still be **moved between organizations** later if needed.)
**Steps:**
1. Login to the desired organization
2. Navigate to **Organization > Inventory & License > Licenses**
3. Click on **"+ Add License**" on the top right
4. Enter the license key
5. Click “**+ Add License**” again and follow the prompts to complete the claim process.
After confirming the license addition, you can view the license details — *such as license status, forced activation date (in the Activation Date field), issued date, duration, etc.* — **under Organization > Inventory & License > Licenses.**\
For example, PRO Licenses will appear under the PRO tab, and Cloud AI Licenses under the Cloud AI tab.
### **MSP License Claim & Extend the MSP Portal’s validity period**
With the **MSP Group–based Licensing model**, MSPs can claim and extend licenses via the MSP Portal.
1. **Claiming an MSP License**
* Navigate to MSP Portal in the left-hand menu bar.
* Enter the provided license key and click “+Add MSP License”
2. **Extending** M**SP Portal’s Validity** wit**h Multiple MSP Licenses**
* Navigate to **MSP Portal > Inventory & License > Licenses** page.
* Click “**+ Add License**” at the top left.
* Enter the new MSP license key and confirm to extend the MSP Portal’s validity period.
{% endstep %}
{% step %}
## Customer can assign license(s) to a device (only for Per-Device Licensing)
Users can assign a Per-Device Licensing model to a device to:
* **Extend the validity period** of a Pro license for each product category or the Unlimited AI license.
* **Expand** SecuPoint VPN user seats.
You can assign licenses to devices in two ways:
### **Automatic Binding:**
When adding a license, enable the “**Auto Associate**” option to have licenses automatically associated with matching devices.
* **Steps**
1. When adding a license to an organization, license information pop-up window will appear.
2. Enable the “**Auto Associate**” option.
3. Click “**+ Add License**” at the bottom right to proceed.
4. If the licenses correspond to devices within the organization (e.g., ECW230S), a list of eligible devices will be displayed.\
**Note.** The EnGenius Cloud system will **prioritize** devices with the **earliest license expiration date** for automatic association.
5. Click **Confirm** to complete the process.
6. After confirming the license addition, you can view license-to-device binding under **Organization > Inventory & License > Licenses**. \
For example, PRO Licenses will appear under the **PRO** tab, and Cloud AI Licenses under the **Cloud AI** tab.
### Manual Binding:
If you prefer to assign licenses **manually**, there are two options:
1. Go to **Organization > Inventory & License > Licenses** (e.g., Pro tab), select the license(s) that are not yet associated with any device, and click Associate to Device (top right) to bind the license(s) to specific devices.
2. Go to Organization > Inventory & License > Devices, select a device, and in the “Actions” field click “**Assign License**”. If multiple licenses of the same type are available with different durations, you can choose the desired duration to bind to the device.
{% endstep %}
{% endstepper %}
---
# 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/engenius-licensing-ordering-claiming-and-assigning.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.
