> 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/doc-plugins/plugins-glpi/tag.md).

# Tag

## Sources

| Download                                      | Sources                              |
| --------------------------------------------- | ------------------------------------ |
| <https://github.com/pluginsGLPI/tag/releases> | <https://github.com/pluginsGLPI/tag> |

***

## Requirements (self-hosted)

| GLPI Version | Minimum PHP | Recommended |
| ------------ | ----------- | ----------- |
| 11.0.x       | 8.2         | 8.4         |
| 12.0.X       | 8.3         | 8.5         |

{% hint style="info" %}
This plugin is available without a [GLPI Network](https://services.glpi-network.com/#offers) subscription. It is also available on [GLPI Cloud](https://glpi-network.cloud).
{% endhint %}

***

## Install the plugin

* Go to the marketplace. Download and install the plugin "**Tag**".

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2FZOA8V8M4VUrLuYEca0qL%2Ftag.png?alt=media&amp;token=afeabc58-b5d4-4cb8-abc1-b6f5c0967f01" alt="images/Tags-1.png"><figcaption></figcaption></figure></div>

***

## Setting up the plugin

* From **`Setup`** > **`Dropdowns`**
* Click on **Tag management**
* Then **Tags**

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-e997d2419adb8da0f9d55db2c47b546b175e12c9%2FTags-2.png?alt=media" alt="images/Tags-2.png"><figcaption></figcaption></figure></div>

* Enter a name that will be visible when tags are added
* Enter a description (optional)
* Add a colour
* Associate one or more elements. If nothing is ticked, it will not be visible in any element by default.

<figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-e1602fc7a1372c8a05c7edac271eff8371a6bcc7%2FTags-3.png?alt=media" alt="images/Tags-3.png"><figcaption></figcaption></figure>

### Choose where to find the tag

You can indicate whether the tag should be at the top or bottom of the list.

* From **`Setup`** > **`General`** > **`Tag management`**, specify the tag location.

Bottom :

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-0446f6245f0481f710fc298f696edb5a3036a1b3%2FTags-7.png?alt=media" alt="images/Tags-7.png"><figcaption></figcaption></figure></div>

Top:

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-c7e59db90a6e657208133f0c27cc9a3e3924e8c0%2FTags-8.png?alt=media" alt="images/Tags-8.png"><figcaption></figcaption></figure></div>

***

## Adding rules

You can add business rules (tickets, computers, etc.) to add tags to particular items.

Example : Assign a VIP tag when a member of the management group writes a ticket.

* Here are the criteria to be implemented from **`Administration` > `Rules` > `Business rules for tickets`**

<figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-f8b5c5a11da67465abf17b83740738aebb600eab%2FTags-4.png?alt=media" alt="images/Tags-4.png"><figcaption></figcaption></figure>

<figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-007d185852c31cd12d9dacd8b6fbd61112fc669f%2FTags-5.png?alt=media" alt="images/Tags-5.png"><figcaption></figcaption></figure>

* After creating a ticket :

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-58bbd737fcce1dc763d19b9891f69c84507282dd%2FTags-6.png?alt=media" alt="images/Tags-6.png"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Tags can, of course, be added manually if they have been set to be visible in the specified item.
{% endhint %}

***

## FAQ

If you have any questions about using the plugin, please consult our FAQ

<a href="/faq/plugins/tag.md" class="button secondary">Go to FAQ</a>


---

# 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/doc-plugins/plugins-glpi/tag.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.