> 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/license-entitlements/license-start-date.md).

# License Start Date

When issuing a license, you can set a start date for it. Adding a start date to a license will prevent license activations until that date. This can be useful to fine-tune usage of a rented or time-limited license, or to make software available only for an academic term, for example.

### Issuing Licenses With a Start Date

Navigate to the product selection screen during the process of issuing licenses. Toggle the "Use custom license values". Under license usage, there is a field called "License Start Date" where you can specify the start date.

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/o7Hz2Upy4yzzWjOoRW0E/B0cp7IFFtLQvmWbH_Cm4j_image.png)

### Add/Modify/Remove the Start Date of an Existing License

{% hint style="info" %}
If you set a start date on an existing license that had already been activated, it will not affect the license that has already activated it. Instead, it will simply prevent additional license activations until the start date.
{% endhint %}

Navigate to the license detail screen and press "Edit License". From there you can set or delete the "License Start Date".

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/QT0TNpm8BbLP6D5e0WVH/LszV%20b4o_jHvMLbn7Y0wb_image.png)

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/wvNKr04Gnf6OTRNdUyus/83mXCRCk6pgE1EGw8JNdE_image.png)


---

# 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/license-entitlements/license-start-date.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.