> For the complete documentation index, see [llms.txt](https://athome-1.gitbook.io/athome-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://athome-1.gitbook.io/athome-docs/management/licenses.md).
# Licenses
Licenses management in GLPI allows to manage software licenses:
* Inventorying licenses, with links to software inventoried in GLPI;
* Following license installations on all assets;
* Linking licenses to financial management;
* Anticipating and following licenses renewal.
{% hint style="info" %}
A license cannot exists in GLPI without a software associated to the license when creating it.
License management is not automated, a human follow-up is needed for information update.
{% endhint %}
{% hint style="info" %}
It is possible to use [templates to generate this object](/athome-docs/overview/template-management-in-glpi.md).
{% endhint %}
## Description of specific fields
* **As child of**: allows to specify if the license is dependent upon another license;
* **Version in use**: the version of the software associated with the license;
* **Purchase version**: the purchase version, which can differ from `Version in use`; if different, this field indicates it;
* **Number**: the maximum number of uses of the license by assets;
* **Allow Over-Quota**: allow or not the overflow of maximum number configured in field `Number`;
* **Expiration date**: expiration date of the license, useful to configure alerts and anticipate renewal.
***
## Licenses
This tab lists all licenses declared as child of this license.
{% hint style="info" %}
Some licenses can be obtained by pack or by group, linking them by child/parent relationship allows to declare it.
{% endhint %}
To add a child license, you need to create a license from software and enter the parent license in the **as child of** field.
To unlink/modify/delete a child/parent, you can modify the entry in this same field
***
## Summary
This tab lists all types and entities of items linked to this license.
{% hint style="info" %}
The number of installations must be carefully checked against the field `Number` of the license.
Creating a link between an asset and the license id done in tab `Softwares` of the asset.
{% endhint %}
***
## Items
This tab details each item linked to the license.
Go to Items
***
## Management
Management of financial and administrative information, this information is visible in the 'Management' tab on the computer's form.
Go to Management
***
## Contracts
GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...
Contracts management allows to:
* make an inventory of all contracts related to the organization assets
* integrate contracts in GLPI financial management
* anticipate and follow contract renewal.
* Documents
The [document](/athome-docs/management/documents.md) tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab.
Go to Contacts
***
## Documents
The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab.
Go to Documents
***
## Knowledge Base
Lists all the articles in the knowledge base relating to the material.
Go to Knowledge base
***
## Notes
The *Notes* tab provides a free text field for storing additional information. Notes are displayed in the order of their creation. You can also add a document
Go to Notes
***
## Certificates
This tab allows to attach a certificate present in GLPI to the license.
Go to Certificates
***
## History
The *History* tab is used to show any changes made to an item. The following information about the changes is available:
* ID of the change.
* Date and time the change was made.
* User who made the change. If this field is not filled, it means that the action was done automatically (For example: automatic inventory update).
* Field that was changed.
* Description of the change that was made.
The description of the change represents either the difference between the old and the new value (For example with location field: Change HQ to Remote Office A), or the explanation of the action which was carried out (For example: Uninstallation of a software: "Gimp 2.0").
{% hint style="info" %}
For dropdowns or objects with a parent/child relationship, the modification of a child will appear in the history of the parent element.
{% endhint %}
***
## All
For an item, all information is displayed on one page from the *All* tab. This shows all of the tabs of an object's form in one view, one below the other.