> 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/faq/glpi/contract.md).

# Contracts

***

### What is a contract?

Contract management in GLPI is designed to provide efficient, centralised management of all aspects of IT[^1] contracts, improving the transparency, traceability and efficiency of IT operations.

For example, contracts can be used to

* **Cost management**: GLPI tracks the costs associated with each contract, including recurring and one-off payments.
* **Budgeting**: financial information from contracts can be used for budgeting and forecasting expenditure.
* **Linking with other modules**: Contracts can be linked to specific assets or equipment, making it easier to monitor equipment coverage and maintenance.
* **Supplier** management: GLPI can be used to manage a directory of suppliers, with detailed information on each one. It is also possible to set up a supplier evaluation system to assess supplier performance in terms of services provided and contracts in force.

***

### What information is available in contracts?

You can enter a range of information to help you manage your contracts and related items:

* Name
* Status
* Contract type
* Start date
* Initial contract period
* Notice period
* Location
* Number
* Account number
* Contract renewal period
* Invoice period
* Maximum number of items
* Renewal
* Email alarms
* Support hours (can be set for weekdays, Saturdays, Sundays and holidays)

Available tabs :

* Costs
* Suppliers
* Items
* Documents
* Links
* Notes
* Knowledge base
* Tickets
* History
* All

***

### Is it possible to link a default contract to an entity?

Yes, from **`Administration`** > **`Entities`** > **`Support`** tab. Select the desired contract in **`Default contract`**.

***

### What notifications are available in the contracts?

To make contract management easier, notifications can be sent:

* End of contract
* End of periodicity
* Advance notice
* Advance notice of period

***

### Why am I not receiving notifications?

This may be due to a number of reasons:

* Problem configuring the [SMTP server](/notifications/setup_notifications.md)
* The contract is not active or no longer active
* The [automatic action](/automatic-actions/configuration_action_auto.md) **`contract`** is not active or incorrectly configured
* Your [cron](https://glpi-user-documentation.readthedocs.io/fr/master/modules/configuration/crontasks.html) is not active or incorrectly configured

***

### Why can't I link my contract to a GLPI object?

If you don't see your contract in the GLPI object in question, you need to check a few points:

* The contract must be active (not expired)
* A start date must be entered
* A duration must be indicated

{% hint style="success" %}
**Expired contracts** are not visible in the various GLPI objects so as not to "pollute" the list of contracts. On the other hand, you can link a GLPI object directly from the contract even if it has expired.
{% endhint %}

***

### Can you edit contract-related reports?

Yes, from **`Tools`** > **`Reports`**, you can select the option **`By contract`**. Select the item type (several items possible) then the year(s).

[^1]: Information Technology


---

# 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/faq/glpi/contract.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.