> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/user-management/license-promo-codes/using-license-promo-codes.md).

# Using License / Promo Codes

The User Management functionality of the Designer allows users to set up Promo Codes, which allow application admins to grant access to LogicNets applications on a temporary basis for a potentially large group of people without the need to formally approve specific users. Promo Codes allow for user self-service to create an account.

Promo Codes can be used to give an anonymous user access to a group account; for example, to show a user what they can do with an account. They can also be used to set up a shared group account using identified email addresses. They give users a fast way to get an account, and the Promo Code tells the system to which group and profile type the user belongs.

Additionally, administrators can specify that the user to whom a code is given can only access the system once or for a specific number of days. The administrator can allow the user to access between specified calendar days.

For more information on how to use license/promo codes, review the [License/Promo Code Help articles](/release-9/design-considerations-and-frameworks/user-management/license-promo-codes.md) here.


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/user-management/license-promo-codes/using-license-promo-codes.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.