> 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/registrations/registration-list.md).

# Registration List

The registrations list portion of the registrations page presents the following key statistics:

* **Aggregated Registration Count per Product**\
  This shows the total number of active registrations for each product, allowing you to quickly assess license usage across your entire product portfolio.
* **Individual Registrations**\
  Each active registration is displayed, detailing the specific user or device tied to the license. This helps administrators manage which users or devices have access to licensed software.
* **Aggregated Consumptions per Product**\
  Alongside registrations, the page provides a summary of the current license consumption, indicating how many licenses are in use for each product.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/IfBUNiXvTsVoghGZbAr9/W9kMGBXX3Bz5U8jP2xh0d_image.png)

{% hint style="info" %}
Managing registrations:\
By removing a registration, you free up a license, allowing another user to register for that product. This flexibility ensures that licenses can be efficiently reassigned without needing to deactivate or revoke them manually. It's particularly useful in environments with a limited number of licenses and multiple users requiring access.

For example, if a user no longer needs access to a product, their registration can be removed, making the license available for another user or device.
{% 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/floating-server/floating-server-v1/user-interface/registrations/registration-list.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.