> 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/create-a-promo-code.md).
# Create a Promo Code
1\. To create a Promo Code, click on the *Access Management* button on the Designer landing page. 2. On the *User Management* screen click the *Licenses* button.
3\. Click *new* to add a new license.
4\. Complete the *license details* fields.
| Field Name | Details | Example |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------- |
| Code | Free text field. This is the code that is shared with users. | RFSP117122WT |
| Type | Promo or License dropdown. Select Promo. This data is available for reporting. | Promo |
| Start date | Date when code becomes active | 12/01/2017 |
| End date | Date when code becomes inactive | 01/31/2018 |
| Supplied by | Free text field. This data is available for reporting. | Sun |
| Campaign | Free text field. This data is available for reporting. | Sun Pharma Initial Interest |
| No. of Licenses | Number of unique email addresses that can use the promo code. | 300 |
| License length (days) | Number of days between user gaining access and user being blocked from access. | 15 |
| Admin group | Not used for Promo Code. | |
| User group | Group to which all code users are assigned. This allows for managing access to packages and tools. | RFSP117122WTusers |
| Status | Status of Promo Code (Inactive, Active, or Expired) | Active |
| Visibility | Public: Users can activate a Promo Code in the LogicNets application.
Private: A user administrator must activate the user's account.
| Public |
| Autoactivate | If the checkbox is not clicked a user administrator must approve new user accounts.
If the checkbox is clicked the system can activate the user account immediately.
| Check = Yes |
| Only single use allowed | If the checkbox is not clicked the code can be used by multiple users.
If the checkbox is clicked only a single user can use the code.
| Check = Yes |
5\. As necessary, complete the license reminders to have the system send a user a first reminder, second reminder, and expiration reminder. To have the system send the reminders, click the checkbox next to the reminder type.
6\. Click *Save*.
---
# 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/create-a-promo-code.md?ask=&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.