> 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/assets/tabs/softwares.md).

# Software

This tab, named `Softwares` and visible in a `Computer` entry, allows to manage the software installed on a computer. Those software are sorted by their category and are characterized by name, version and version status.

To install a software, first select its name in the drop-down list, then its version.

It is possible to associate a license to a software on a computer.

To associate a license, first select the software in the drop-down list, then the wanted license.

If the license is associated with a software that is already installed on the computer, it will be presented in the list of software.

Otherwise it will be displayed in a separate table.

{% hint style="info" %}

* the drop-down list enumerates the software that are available in the entity
* licenses management can be found in \[Assets > Softwares]{.title-ref}. See [Manage software](https://help.glpi-project.org/documentation/modules/assets/softwares.md)
  {% endhint %}

{% hint style="info" %}
It is possible via mass actions to install on a computer a software selected from its license.
{% endhint %}

{% hint style="info" %}
Every deletion or addition of a software or a license is recorded in the history of the computer.
{% endhint %}

{% hint style="info" %}
If using native inventory or third-party inventory tool, the software information can be automatically imported and updated.
{% endhint %}


---

# 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/assets/tabs/softwares.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.
