> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/assistance/recurrent-changes.md).

# Recurrent changes

## Overview

**Recurrent Changes** is a major new feature in GLPI 11 that automates the creation of change requests on a periodic basis.

## Why use it?

* Automatic creation of changes according to a defined frequency
* Use of predefined change templates
* Calendar management to comply with working hours
* Advance creation to enable planning
* Support for entities and recursion
* Simple activation/deactivation

## Prerequisites

**Required profile**: “Recurrent changes” right (read/write as needed)

**Access to templates**: “ITILTemplate” right to configure templates

## Configuring **recurrent changes**

### **Navigating the interface**

* In the main menu, click on **Support**
* Select **Recurrent changes** from the submenu
* On the Recurrent changes page, click **Add**

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FXe1mGEofrBdiyiXXT3bE%2Fadd_recurrent_change.png?alt=media&amp;token=fd8b2cc2-7491-463d-ada0-e7c86120a5af" alt=""><figcaption></figcaption></figure>

### **Basic configuration**

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FLC5WK7sidPpnCl40Nx2K%2Fbasic_info_recurrent_change.png?alt=media&amp;token=57b2f3ce-86c0-491e-8415-aa50fe163c2d" alt=""><figcaption></figcaption></figure>

* **Name**: Descriptive name of the recurring change
* **Comment**: Description of the recurring change *(optional)*
* **Active**: Enable/Disable the creation of recurring changes

### **Adding the change template**

When creating the change, GLPI will use the configuration of the associated template. This is useful for configuring predefined, mandatory and hidden fields.

### **Time configuration**

**Start date**: Date from which to start the recurrence

**End date**: Automatic stop date *(optional)*

**Periodicity**: Waiting time between the creation of two recurring changes

**Preliminary creation**: Time limit for creating the change before the start date (up to 2 weeks) *(optional)*

**Calendar**: Restriction to working hours (optional)


---

# 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://help.glpi-project.org/documentation/modules/assistance/recurrent-changes.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.