> 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-v1/user-interface/ui-configuration/products.md).

# Products

Products tab can be found under Configuration page. It allows you to add new licenses associated with products and see which ones you already have installed.

The Products tab, located under the Configuration page, allows you to manage products and their associated licenses. A license is an instance or usage right of a product, and multiple licenses can be created for a single product to accommodate different use cases, users, or devices.

### Install a Product

#### License Key Authenticated Product

To install a key authenticated license, you need the product's code and license key. Simply select "Key auth" from the dropdown and add product information to the corresponding fields.

After a license is added using the **product code**, its corresponding **license ID** will appear in the list of licenses on the **Products** page. This functionality was introduced in version 1.6.0, when the floating server began supporting multiple licenses for each product. This enhancement allows users to add an unlimited number of licenses for a single product.

{% hint style="warning" %}
**Note:** Products need to be added using product code, not product name.
{% endhint %}

![Key Authenticated Product](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/ISp8470Lf5txpfdXDH9G/cC2YR3_JQTzchbMeB1fW7_screenshot%202023%2006%2021%20at%20141733.png)

#### Password Authenticated Product

You can also install a password authenticated product. To do that, you need to know a product's name as well as username and password that can authenticate that product.

Select "User auth" from the dropdown and fill the form for password authenticated product.

![Password Authenticated Product](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/Fsr0eIx95I6ogOxDUjBZ/9xT3JjPkioBdBeZkGvRa5_screenshot%202023%2006%2021%20at%20141755.png)

#### Offline Licenses

Floating server also allows you to install offline licenses. To do that, visit the [**Generate Offline License**](broken://pages/841ff27a5d5007fea2cfbf0a92d615d4c9f51ee4) page and follow the instructions. Afterwards, activate the offline license like this:

![Offline License Activation](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/YvkEoqHpSyvwVlu8hnnw/K4cGljTslXNLqGCTTWfwl_screenshot%202023%2006%2021%20at%20141807.png)

### Listing Installed Products and Removing Them

Products page allows you to see which products you have currently installed as well as remove them.

![Installed Products](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/JSGzcUMQQPasqRnSR5iO/0a2qcpf2%20lqA%20T%20h8X1pI_image.png)


---

# 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-v1/user-interface/ui-configuration/products.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.