> 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/device-pro-license-overview/pro-license.md).

# Pro License

## <mark style="color:$primary;">Terminology</mark>

EnGenius Cloud includes network hardware devices and a cloud platform, consisting of two essential components: an “Organization” and a “Network.” The following defined terms are used in this License Agreement. &#x20;

<table><thead><tr><th width="278.66493847293464">Term</th><th width="402.3699077389575">Description</th><th data-hidden data-type="users" data-multiple></th></tr></thead><tbody><tr><td><strong>Associate</strong></td><td>Associate means to bind a License to a specific device.</td><td></td></tr><tr><td><strong>Associated Device</strong></td><td>A device with at least one associated License.</td><td></td></tr><tr><td><strong>License (or “Device License")</strong></td><td>One unit of usage rights granted to you and which can only be associated to one and only one device.</td><td></td></tr><tr><td><strong>License Activation Date</strong></td><td>The date on which a Device License commences, and thereby begins the licensing term.</td><td></td></tr><tr><td><strong>License Key</strong></td><td>A unique passcode (key) that a subscriber receives after the order is placed. A License Key may comprise multiple units of License of the same License model.</td><td></td></tr><tr><td><strong>License Issued Date</strong></td><td>The date that a license key is issued.</td><td></td></tr><tr><td><strong>Org Feature Plan</strong></td><td>The feature set available under different feature plans, including but not limited to a Basic Plan and a Pro plan, in the Organization.</td><td></td></tr></tbody></table>

## <mark style="color:$primary;">License Activation</mark>

### Scenarios to activate Cloud licenses

Each EnGenius Cloud Pro license comes with a validity duration (depends on the license model you purchased) and will remain active after being activated until it is expired.

There are two ways to activate a license&#x20;

![Diagram 3 - Scenarios to activate Cloud licenses](https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FwjDxCiGIsOkgSdwjjrTZ%2Fimage.png?alt=media\&token=17184e44-6e3e-435b-b1c2-936ffc9463e7)

### **Manual Activation**&#x20;

**Associate licenses to the device and assign the device to a Network**

When you assign this license-associated device to any network in your organization, the license will start to activate and operate during its validity period. For example, Device A/B are assigned to Network 123 and 456, so AP-License 1 and 2 are activated from the date they are assigned to the Networks.

{% hint style="info" %}
The license associated with the device will not be activated during the planning period **until the device is assigned to Network** and apply the configuration.
{% endhint %}

### **Forced Activation**&#x20;

**No license association or network assignment after 90 days of licenses issued**

Suppose you have never associated the license with any device, or the license-associated device has not been assigned to any managed network. In that case, this license will be automatically turned into an active state after it is issued for 90 days. *(Device C, diagram 3)*

{% hint style="info" %}
After a license is forced activation, the validity period would **start** to **burn**. No matter the license is associated with a device or not.
{% endhint %}

## <mark style="color:$primary;">License Expiration</mark>

The validity period of the license for each device managed by EnGenius Cloud is independent. If the license of one device has expired, it will not impact other devices with valid licenses. You can still use the professional features and manage these devices whose licenses are still valid.&#x20;

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FAEL9rEwCxTL8kV7gzvel%2Fimage.png?alt=media&amp;token=a109b5c8-adb0-4015-981d-8fe44afa5b8c" alt=""><figcaption></figcaption></figure>

<p align="center">Diagram 4 - License expiration for devices</p>

### **When the license of a device in the managed Network expires:**

* When one of the devices exceeds the expired date of its license, the license-expired device is still functional as usual, but cannot be managed(off-lined) by EnGenius Cloud or using any Cloud-related features like Cloud authentication. *(Device D license is expired and offline)*

* When a device’s license expires, it will continue to function as usual. However, in EnGenius Cloud, **ONLY its online or offline status** will be visible. As a result, the device can no longer be managed through EnGenius Cloud, nor can it use any cloud-related features, such as cloud authentication.\
  *(For example: If Device D’s license has expired, only its online/offline status will be displayed.)*

* The other devices within the same Network with a valid license won’t be affected by the use of professional features. *(Device A\&B will still be managed even Device D license is expired)*

* If the Feature Plan is changed **from PRO to Basic**, all your devices (expired or active) can then be managed by EnGenius Cloud, all privileges exceed Basic limit will be erased and Pro features will be disabled. (see [Feature Plans Comparison](https://www.engenius.ai/cloud/licenses))&#x20;

{% hint style="info" %}
For a license-expired device, to manage it with EnGenius Cloud again:&#x20;

1. Add a new license to the device (with professional features)
2. Change the Feature Plan from PRO to Basic. (without professional features)&#x20;
   {% endhint %}

## <mark style="color:$primary;">License Status & Lifecycle</mark>

The following diagram reveals the various statuses and operations performed on a license.

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FuJP8uNfvoiK4UG7oy2dg%2Fimage.png?alt=media&amp;token=5a113a3b-63f2-4312-8e8b-876815f7a73d" alt=""><figcaption></figcaption></figure>

| Terms                        | Description                                                                                                                                                               |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **License Key Issue Date**   | The date when a license key is issued and mailed                                                                                                                          |
| **Activation Date**          | The date a licensed-associated device is assigned to a managed network.                                                                                                   |
| **Forced activtion Date**    | The date that the license is auto-activated because of no activation on any device after 90 days of being issued.                                                         |
| **Expiration Date**          | One year or three years after the license activation date. For a licensed device, the expired date means extending the validation of its original expired date            |
| **Order Return**             | The license order can be returned within one month after the license key is issued. (This is subject to the operation of each region. Please contact your local EnGenius) |
| **Undo License Association** | You can disassociate the license from a device within seven days after it's associated.                                                                                   |

## <mark style="color:$primary;">Add License</mark>

To enable professional features for managed devices, you need to purchase **PRO License Key** from EnGenius resellers first and add it to your managed **Organization**.&#x20;

### **Adding a license to the Organization**

1. Login to EnGenius Cloud and select the managed Organization
2. Go to ***Inventory & License > Licenses***
3. Click ' **+ Add License**' on the right
4. Enter the **purchased license key(s)** and the system will unzip the license key(s) into one or multiple licenses. Click "OK", adding to Organization
5. All licenses added will be displayed in the license table with related license information.

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FmSe7Id3itc5f5IMyY218%2Fadd%20license.PNG?alt=media&amp;token=aeb2925d-d623-424e-94d5-accd7e3af56a" alt=""><figcaption><p>Figure 1 - Assign license to organization</p></figcaption></figure>

## <mark style="color:$primary;">Associate License</mark>

Associate a license means to bundle a license to a specific device.&#x20;

After you select PRO Feature Plan and already added license to the Organization, you need to associate license(s) to the device(s) and assign the device(s) into a managed Network, thus those devices can use Professional features. &#x20;

### **Associate license(s) with the device(s)**

1. Login to EnGenius Cloud and select the managed Organization
2. Go to ***Inventory & License > Devices***
3. Click ' **+ Assign License**' at the right of each device&#x20;
4. Select any available and valid license(s) to associate it to the device&#x20;
5. License-associated device(s) will display the information for license status and the expiration date.

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FeslZEWlsylhDDfnU6kQy%2Fnew%20device.PNG?alt=media&amp;token=fb82bd3b-2b59-4b43-a368-ad7db949413d" alt=""><figcaption><p>Figure 2 - Assign license(s) to a device</p></figcaption></figure>

{% hint style="info" %}
If more than two licenses are installed on the same device within a 7-day Undo period, only one license can be disassociated, and the remaining licenses cannot be disassociated.
{% endhint %}

## <mark style="color:$primary;">Move License</mark>

EnGenius Cloud licensing allows administrators to move the licenses and devices between Organizations in the following use cases.

* Move device(s) and transfer associated licenses to another Organization&#x20;
* Move unassociated licenses to another Organization directly

{% hint style="info" %}
When you move around licenses and devices between Organizations, you need to have privileges (**Organization administrator**) on both sides.&#x20;
{% endhint %}

### Moving unassociated licenses&#x20;

* Only the unassociated license, the license with the empty association, can be moved to another **Organization**&#x20;

### Moving device(s) with licenses&#x20;

* When the device is moved to another **Organization**, the associated licenses will be moved simultaneously.
* The license information will remain the same whenever you move devices (associated licenses) to another Organization.
  * License Issue date
  * License Activation date
  * License Status

![Move device B with licenses between Organization (From Organization A to Organization B)](https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FD6psuf8ZTlrOIiadzvNg%2FMove%20device%20nad%20license.jpg?alt=media\&token=1a9ea3c8-7e21-4123-9903-d57eed25a880)

## <mark style="color:$primary;">Replace Device</mark>

The **Replace Device** feature is commonly used when a device experiences **hardware failure** or during an **RMA** (Return Merchandise Authorization) process, allowing an existing device (such as an Access Point, Gateway, or Switch) to be replaced with another new device (Replacement device). The new device will automatically <mark style="color:purple;">**inherit**</mark> the **configuration** and **licenses** of the original device without the need for manual reconfiguration, significantly reducing deployment time and minimizing administrative effort.

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FYarvT6o2EfP6ACMlrWhb%2Fimage.png?alt=media&amp;token=16de8225-fb94-4adc-9644-30753f2bd170" alt=""><figcaption></figcaption></figure>

### Replace Device in EnGenius Cloud Dashboard

1. Login to EnGenius Cloud and select the managed Organization
2. Go to ***Inventory & License > Devices***
3. Add the replacement device to the same Organization.

{% hint style="info" %}
Note: Do not assign this device to any Network at this step.
{% endhint %}

4. Click “**Replace**” at the right of the faulty device.
5. Select the replacement device and click Apply.

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2Fb61QYsUH0JYUSu7I9ZK5%2Fimage.png?alt=media&amp;token=e6d15059-8cc2-4e5e-9ca4-6ddb18c61c5e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note.**

1\.      The faulty device will be automatically removed from the original Network, and the replacement device will automatically be bound to the same Network, **inheriting** both the **License** (with consistent license status) and **configuration** files.

2\.      If the new device (replacement device) already has active licenses, those licenses will be changed to **Canceled** status. Therefore, it is strongly recommended to ensure that the replacement device does not have any active licenses before performing the replacement.
{% endhint %}

6. The replaced faulty device’s license status will be marked as **Expired**.

<figure><img src="https://1823096013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5DPQa0cw0ZPNxF9jZEXv%2Fuploads%2FRHDVHymP7LcQG0DCvp7i%2Fimage.png?alt=media&amp;token=a5f0ddd8-9717-46a9-a90d-4a169c864a92" alt=""><figcaption></figcaption></figure>


---

# 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://doc.engenius.ai/cloud-licensing/device-pro-license-overview/pro-license.md?ask=<question>&goal=<user_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.
