> 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/vendor-platform/license-users.md).

# License Users

This page lists all license users that have been added to a LicenseSpring account. A license user typically is added to LicenseSpring at the moment they are assigned to a given license. A license user represents an individual who can access and use a product under a user-based licensing model.

![License Users Page](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/sofBDCjqY52ss4Pakmsn/Aogob3ddfwBhmgSZcp964_image.png)

## Searching for License Users

You can search for a license user to find all the licenses they are assigned to. The following search criteria are supported:

* First Name
* Last Name
* Email
* Phone Number

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/u8u8Tqpx9ZXJPtM1kQiv/2bv5Xat59f1EGr1ZT1%20TM_image.png)

## Individual License User Information

After selecting a license user, you will see the User Details screen, where you can inspect the user’s information across three main sections: licenses, devices, and user groups.

### Licenses Tab

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/2Gcjtm0XPyRwB1n3HPwm/_0TQEsKnAbhQU5inoZTWu_image.png)

This table displays all licenses currently assigned to the user. You can view key details including:

* Created On: Date and time the license was issued.
* User: The assigned user’s email.
* Product: Name of the licensed product.
* Product Features: Specific features included in the license.
* License Type: Type of license (e.g., perpetual, subscription).
* Expiration Date: When the license will expire (if applicable).
* Times Activated: Number of times the license has been activated.
* Is Trial: Indicates if the license is a trial version.
* Status: Current state of the license (e.g., active, inactive).

{% hint style="info" %}
**Initial Password** This is the password automatically generated when a user is first added to LicenseSpring. Users are prompted to change it on first login.

The initial password is shown only until the user changes it. After that, it is no longer displayed in the platform or returned by the Management API.
{% endhint %}

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/Ys6STBN0Vv9aqPUcJLHA/CiiGYZSvKZzyqzzboJxqV_image.png)

### Devices Tab

The `Devices` tab lists the devices the user has activated, across all their licenses, 20 per page. Click a row to open the device.

With permission to manage licenses, you can act on the devices:

* **One device:** click `Reset` in its row. Only active devices can be reset.
* **Several devices:** tick them, open `Bulk Actions` and choose `Reset devices`, `Blacklist devices` or `Whitelist devices`.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FE1Adh0E2hnrHACgIYo6Y%2F22-platform-user-page-devices.png?alt=media&amp;token=24d2f83f-0a1a-4a4e-8c6e-e4dcf6f9d1c2" alt=""><figcaption></figcaption></figure>

When you reset several devices and some of them are inactive, the confirmation tells you how many are skipped, because inactive devices have nothing to reset.

Use `Go to license` in a row to open the license the device is activated on.

> A selection covers the current page only. It is cleared when you go to another page.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/n7Z5kdVf9hW9hW4hKa1X/6188dF5j2j5D1Vid%20AELX_image.png)

### User Groups Tab

* Lists any user groups the user belongs to.
* User groups help simplify license management. On the User Group page, you can easily assign users, allocate licenses, and designate license managers.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/tauL4xiwcKlA1dQt4TXg/JZmY35u4ebSyIlb7%20QHmc_image.png)

### Change a license user's password

You can set a new password for a license user, or send them a link to set one themselves. Open the license user and click **Change password**.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FZcrym2MJaGfIehuxoANy%2FScreenshot%202026-10-30%20at%202.27.30%E2%80%AFPM.png?alt=media&amp;token=678ef606-ac57-4f78-bc95-35640a867a17" alt=""><figcaption></figcaption></figure>

The same **Change password** dialog is available on the **License User**, **License Manager** and **Order Manager** pages.

**Set a new password**

1. Open the license user and click **Change password**.
2. Enter a new password, or click **Generate** to create a strong random password.
3. Check the strength indicator under the password field. The password must meet the password rules below.
4. Click **Confirm** to save.&#x20;

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FAdYs3ZDE63xhQgLAgpYL%2FScreenshot%202026-10-30%20at%202.28.17%E2%80%AFPM.png?alt=media&amp;token=5d552488-c707-4b3c-a994-24b59628888c" alt=""><figcaption></figcaption></figure>

Share the new password with the user through a secure channel.

**Send a password setup link**

Instead of setting the password yourself, you can let the user choose their own.

1. Open the license user and click **Change password**.
2. Click **Send password setup link**.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FjhPrQOJZQgxDl85MxHUN%2FScreenshot%202026-10-30%20at%202.28.53%E2%80%AFPM.png?alt=media&amp;token=e5d433ca-bcd3-47bb-8f17-d9a91eb38adf" alt=""><figcaption></figcaption></figure>

The user receives an email with a link to set their password in the User Portal. The action is recorded in [Audit log v2](https://docs.licensespring.com/vendor-platform/settings/audit-log/audit-log-v2) as `license_user.password_setup_link_sent`.

**Password rules**

{% hint style="info" %}
\[CHECK: list the rules shown in the dialog, e.g. minimum length and required character types] The strength indicator shows how strong the password is while you type. Generated passwords are 12 characters long by default.
{% endhint %}

**Using the Management API**

You can do the same through the Management API:

* `generate_password` returns a generated password. Set `length` from 12 to 128 (default 12).
* `send_password_setup_link` sends the password setup email to the license user.

## Add a new License User

Most users are automatically added to LicenseSpring when assigned a license. If a user does not yet exist in the system and you plan to assign them to a license later, you can also add them manually:

{% stepper %}
{% step %}

### Click Add License User

Open the Add License User dialog.
{% endstep %}

{% step %}

### Enter user details

Provide name, email, phone number and Metadata JSON.
{% endstep %}

{% step %}

### Confirm

After clicking the Confirm button, the user will receive an email containing their initial password.
{% endstep %}
{% endstepper %}

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/q61Icxs3ArN51vPoX1Vf/casBeE42wp61ObvEA%202Ji_image.png)

{% hint style="info" %}
To learn more about user groups, including how to create them and manage licenses, users, and license managers, see the [License Manager Guide](https://docs.licensespring.com/license-entitlements/portal/end-user-portal/license-manager-guide.md).
{% endhint %}

{% hint style="info" %}
User-Based Licensing — Learn how user-based licenses work and review best practices in [User Based Licensing](https://docs.licensespring.com/sdks/tutorials/licensing-scenarios/user-based-licensing.md).
{% endhint %}


---

# 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/vendor-platform/license-users.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.
