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

# Tag

***

{% embed url="<https://www.youtube.com/watch?t=&v=r3Ydl6H1Gvg>" %}

***

### How do I install **`tag`** ?

A [procedure](/doc-plugins/plugins-glpi/tag.md) is available to guide you through the installation and configuration of **`tag`**

***

### What are the functionalities of **`tag`** ?

Tag gives you the ability to add a tag to a GLPI object. You can search for this tag, display a report of associated objects in the administration, or create different administration rules.

You can :

* Add tags on every GLPI item type (which extends CommonDBTM)
* Add tags on GLPI inventory Task (plugin GLPI Inventory)
* Add tags on Appliance (plugin appliance)
* Manage tag from labels
* Tags are displayed and editable in the object form header (just below title)
* You can search for tags and display them in objects lists
* You can display a report from associated objects in administration

***

### Why isn't my tag visible in all categories (tickets, computers, etc.)?

When you create your tag, you can decide in which GLPI object(s) it will be visible. You can therefore create a tag for the computer object only or make it visible for tickets as well.

***

### Why is my tag not visible in my entity?

When creating your tag, if you do not check the **`sub-entity`** box, it will only be visible in the entity where it was created.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.glpi-project.org/faq/plugins/tag.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
