> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/sdks/tutorials/licensing-scenarios/setting-up-user-based-licensing.md).

# Setting Up User Based Licensing

User-based licensing allows software or service assigned to **license users**. Unlike traditional licensing protected with a license key, this approach focuses on the users themselves, making it ideal for tracking, activation limits, and management.

{% hint style="success" %}
This guide walks you through **creating a user-based product, issuing licenses, and assigning users** in LicenseSpring.
{% endhint %}

{% hint style="info" %}
User-Based Licenses can still be node-locked, since LicenseSpring still supports
{% endhint %}

{% stepper %}
{% step %}

### Create a User-Based Product

* Navigate to the **Products** tab in the dashboard.
* Click **Add New Product** (top-right corner).

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/Jdl9en7j0fJZf1PvaUf9/Pkd2yUOCejjiKpiupdGr__image.png)

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/01F0O1p4FXYsdNgK3ga1/CvL7XFN35SkM3RAUltIfH_image.png)

Complete the required fields:

* **Product Name**
* **Product Code**

Optional configurations:

* **Floating Timeout** (minutes): for floating licenses, determines how often the end-user app checks the license to remain registered.
* Product has trial period (You can set the trial period)
* Product has file
* Click **Next** to confirm.

{% hint style="danger" %}
Set the **Authorization Method** to **User:** This ensures that licenses for this product will be managed on a per-user basis, which is required for user-based licensing.
{% endhint %}

* Your product will now appear in the list with **Authorization Method: USER**, indicating it’s a user-based product.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/mn3BrGgnGlNnWEORxVMZ/1LCFHw8Z82Y0HODuV0fin_image.png)
{% endstep %}

{% step %}

### Issue a User-Based License

* Go to the **Licenses** page and click **Issue Licenses**.
* Fill in required fields:
  * **Order ID**
  * **Order Reference**

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/oMguH97h4hvk3VojDhPE/opcmbFHzvcaOt6YQu34e%20_image.png)

Optional:

* Assign a **License Manager** for the order
* Add a customer to the order
* Link the order to a customer account
* Click **Next**.
  {% endstep %}

{% step %}

### Add Products to the License

In this step you add the product to the license.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/hL8PclsAoBJuAKo19Kcz/vH8uq8GyTQ0jiGh79Znub_image.png)

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/HPYx9mHNEWhU6hTP3EOz/xZJFRnAMcscfTC1xAkcps_image.png)

* Select the **user-based product** you created earlier.

Optional settings:

* **License Policy**
* **Air-Gapped Option**
* **Custom License Values**
* Click **Confirm** (top-right) to finalize.
* The newly created product will appear in the product list:

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/IYEtHKnivq0UikOxk0Zo/dw9rRLAR27CCIFn1Tcco7_image.png)

* Click **Next** to review all order information, then select **Confirm** to complete the steps.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/7SKZ7P0Myt7XyHtHW5N8/9prGrXFTiVMCSIESRyfpD_image.png)

{% hint style="warning" %}
At this point, the license exists but **no user is assigned yet**. Under **License Key / User**, it will show **Not Assigned** as illustrated in the screenshot above.
{% endhint %}
{% endstep %}

{% step %}

### Assign a User to the License

* Navigate to the **Licenses** section.
* Select the **user-based license** you want to assign.
* Click **Assign License User**.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/NHleS8FENU4rdUdF486E/VK1RKuMwXnDr1JqhZqeZB_image.png)

Either:

* Select an existing user, or
* Create a new user

Once completed, the license will show the assigned user (e.g. <testuser@licensespring.com>). Please note that only users with **License Manager permissions** can assign licenses to other users.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/FF5wDLQs0VADCYXzsram/74U1kYHnCIOsfL6Uhpy6o_image.png)

{% hint style="success" %}
Users with License Manager permissions can refer to the [**License Manager Guide**](/license-entitlements/portal/end-user-portal/license-manager-guide.md) for instructions on assigning users and managing the User Portal.
{% endhint %}
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/sdks/tutorials/licensing-scenarios/setting-up-user-based-licensing.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.