> 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/glpi-12/overview/status.md).

# Status

Status information is frequently used to sort hardware that is scrapped, available, assigned... It is possible to create new status values specific to the information system managed by GLPI.

<figure><img src="https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2FT0Yl3lTzlTdvesA6IjyB%2Fstatus-asset-en.png?alt=media&amp;token=da9652bd-89aa-46a2-b8bd-e9f83bb77dce" alt=""><figcaption><p>Statuses of items</p></figcaption></figure>

The definition of new statuses and the types of objects for which they will be used is the responsibility of the GLPI administrator and can be created from **`Setup`** > **`Dropdowns`** > **`Statuses of items`**. These defined statuses can be recursive, to facilitate management.

Changing the status of an asset can be done either from the asset's form or by using mass actions.

***

## Report

A [report](https://help.glpi-project.org/glpi-12/tools/reports.md) can display a summary of statuses sorted by asset types. The [global inventory search](https://help.glpi-project.org/glpi-12/assets/global.md) allows querying inventory items by status.


---

# 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/glpi-12/overview/status.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.
