> 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/license-reminder-email-templates.md).

# License Reminder Email Templates

### Description

Use license reminder email templates to trigger the system to send emails to licensees before and/or after the license period has ended. LogicNets' Access Management module allows you to send up to three reminders.

### Steps to Activate a Reminder Email

1. Activate a template by checking the *Send Reminder* box.
2. Enter the number of days prior to the license expiring the system should send the reminder. If you enter a negative number of days, the system sends an email after the license expires.
3. \[Optional] Add a cc email address to have the system send a copy of the reminder.
4. Enter the subject line for the email.
5. Enter the message body, including any email merge fields (see below).
6. Click *Save* and continue to the second and third reminder templates, as required.

### Email Reminder Schedule

The Access Management module checks on a daily basis for any triggered email templates. This is done at the same time each day (most likely at the time of original installation), and at the same time as regular password expiry and account expiry reminders are created. Note that this system cronjob is not visible in the licensed CronJob Scheduler (if available for your account).

### Email Merge Fields

When you create a license reminder email template, you can use variables that will display the license details in the email.

* **Activation Date/Time:** $(datetime(reminder.activation\_date, 'date\_time')) The format of the date/time will match the localization settings of the System Configuration package. Alternatively, you can specify a custom date using the [Date Formatting Shortcodes](/release-9/platform-documentation/other-help-articles/formatting-dates-additional-information.md) listed here; for Example: $(datetime(reminder.activation\_date, 'date', { date\_format\_str = "%A, %d %B %Y" })) will be displayed as "*Your trial license was activated on Saturday, 04 March 2023."*
* **License End Date/Time:** $(datetime(reminder.end\_date, 'date\_time')) You can use date/time construction like those above for this field.
* **License Details (Campaign, Sponsor):** $(reminder.campaign), $(sponsor)
* **Licensee Details:** $(email)

Added for Release 8.1+

* **Licensee First Name**: $(firstname)
* **Licensee Last Name** : $(lastname)
* **Licensee Company**: $(company)

### Using Styling/Formatting in Email Templates

Many email engines reject or delay loading images and formatting for speed and security reasons. We can help you create an email template that that has the same look across multiple email engines and allows features to be loaded on opening. Speak to your LogicNets representative if you would like to discuss this topic.


---

# 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/license-reminder-email-templates.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.