> 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/floating-server/floating-server-v2/admin-and-user-operations.md).

# Admin and User Operations

### User Management & Role-Based Access

The Floating Server has two types of users:

{% stepper %}
{% step %}

### Administrators

* Manage the server.
* Activate or deactivate licenses by adding or removing them from the Floating Server.
* Manage users who can register (check out) licenses.
  {% endstep %}

{% step %}

### Management Users

* Managed by administrators.
* Can register/unregister to licenses added to the Floating Server.
* Can send license and feature consumption data back to the server, usually via a client application.
  {% endstep %}
  {% endstepper %}

{% hint style="success" %}
Authentication:

* By default (`DisableUserAuth: false`), both admin and user actions require authentication.
* If `DisableUserAuth` is set to `true`, user-level actions can be performed without logging in. Admin actions will still require authentication. This is not recommended for production environments.
  {% endhint %}

### Web UI

The Floating Server includes a web UI. What you see depends on your role.

#### What each role sees

Users with the `user` role do not see the following:

* Configuration
* User management
* Offline/Airgap Licensing
* Adding or deleting licenses
* Sync
* Device actions
* Release and unregister buttons for other users

{% hint style="info" %}
With `DisableUserAuth` set to `true`, the release and unregister buttons stay visible for everyone.
{% endhint %}

#### Secrets on the Configuration page

The API key, shared key and client secret on the Configuration page are write-only. They are never shown again after you save them. If you leave a field empty, the stored value stays unchanged.

#### Passwords

Password forms list the password rules and ask for the password twice. After a password change, the user's other sessions are signed out.

#### User Setup

* Admin adds each user to the server.
* Admin sets an initial password and shares it with the user.
* On first login, the user must change their password via:

> POST /api/v5/auth/change-password

{% hint style="info" %}
For a complete list of API calls for admins and users, refer to the Swagger documentation.
{% endhint %}

### Administrator Actions

> Authentication required: Yes

{% stepper %}
{% step %}

### User Management

* Login: POST /api/v5/auth/login
* Add user: POST /api/v5/auth/add-user
* Remove user: POST /api/v5/auth/remove-user
  {% endstep %}

{% step %}

### Administrators — License Operations

#### Online Licenses

* Add license: POST /api/v5/license
* Remove license: DELETE /api/v5/license/{id}

#### Offline Licenses

* Generate offline activation request: POST /api/v5/license/offline/activation/generate
* Upload and activate license file: POST /api/v5/license/offline/activation/upload
* Generate offline deactivation request: POST /api/v5/license/offline/deactivation/generate

#### Air-Gapped Licenses

* Generate activation code: POST /api/v5/license/airgap/generate
* Upload license file & confirmation code: POST /api/v5/license/airgap/activate
* Generate deactivation code: POST /api/v5/license/airgap/deactivate
* Deactivate using confirmation code: POST /api/v5/license/airgap/activate
  {% endstep %}
  {% endstepper %}

### Passwords and Sessions

#### Password rules

From v2.7.0, new passwords must:

* be at least 12 characters long
* be no longer than 72 bytes (characters outside basic Latin can take more than one byte)
* contain at least 3 of: lowercase letters, uppercase letters, digits, symbols
* not be the same as the username

To change a password, the user must be logged in: `POST /api/v5/auth/change-password`. Changing a password signs the user out of all other sessions.

#### Login lockout

After 10 failed logins from the same client IP address, login attempts from that address are blocked for 15 minutes. During the block, the server responds with `429 Too Many Requests` and a `Retry-After` header that says when to try again.

#### Sessions

A session ends after `SessionMaxAge` (default 7 days), and the user must log in again. Logging out ends the session immediately.

### Bundle Management

* Add bundle: POST /api/v5/bundle
* Remove bundle: DELETE /api/v5/bundle/{code}

{% hint style="info" %}
Admins can also perform all actions that users are allowed to do.
{% endhint %}

### User Actions

Authentication required:

* Register/unregister to licenses:

> POST /api/v5/license/{id}/user/register\
> POST /api/v5/license/{id}/user/unregister

* Register/release features:

> POST /api/v5/license/{id}/feature/register\
> POST /api/v5/license/{id}/feature/release

* Add license or feature consumption:

> POST /api/v5/license/{id}/consumption/add\
> POST /api/v5/license/{id}/consumption/feature/add

### JWT Authentication

* Obtain a JWT token:

> POST /api/v5/auth/login

* Include the JWT in the Authorization header for all authenticated requests:

Authorization: Bearer

### Example Floating License Flow

{% stepper %}
{% step %}

### Create user

Admin creates a user.
{% endstep %}

{% step %}

### Initial password change

User logs in and changes their password.
{% endstep %}

{% step %}

### Obtain JWT

User logs in again to obtain a JWT.
{% endstep %}

{% step %}

### Add license

Admin adds the license: POST /api/v5/license
{% endstep %}

{% step %}

### Register license

User registers to the license: POST /api/v5/license/{id}/register
{% 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/floating-server/floating-server-v2/admin-and-user-operations.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.
