> For the complete documentation index, see [llms.txt](https://docs.soraco.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soraco.co/docs/how-to/how-to-embed-a-number-in-the-license-key.md).

# How to embed a number in the license key

If your application needs to enforce a limit of some sort such as number of records that a user can create or the number of accounts they can create to login to your application, you can use the QLM Floating Seats feature to embed this number in the license key. The approach suggested below will only work if you are not using floating seats for their original purpose which is to support concurrent licensing (with QLM Enterprise).

To embed a number in the license key:

* Create a new license key from Manage Keys / Create
* On the create dialog, set "Floating seats" to the required number.&#x20;
* Set all other fields as needed and click OK
* An activation key will be created

Once activated, the number of floating seats will be embedded in the Computer Key.

At runtime, you can determine the number of floating seats as follows:

* Call **DefineProduct**
* Call **ValidateLicenseEx** (computerKey, computerID)
* Call **NumberOfLicenses** to get the number of floating seats


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.soraco.co/docs/how-to/how-to-embed-a-number-in-the-license-key.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
