> 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/management/contacts.md).

# Contacts

GLPI users are the persons having an authentication for the GLPI application. External persons, usually associated with contracts, are known to GLPI as `Contacts`.

A contact is characterized by usual identity information as well as title, phone number, mail address... Defining a list of contact types allows to sort contacts by types. It is also possible to export a contact in vCard format.

![A contact in GLPI](https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2Fgit-blob-5572d3f5a38efe45c0d03f45a1a08eb2ff7b110b%2Fcontact-en.png?alt=media)

{% hint style="info" %}
The list of possible titles for a contact is the same as the list of possible titles for users.
{% endhint %}

***

## Suppliers

The *Suppliers* tab is used to show or add linked suppliers.

<a href="https://help.glpi-project.org/glpi-12/management/suppliers.md" class="button secondary">Go to Suppliers</a>

***

## 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.

<a href="https://help.glpi-project.org/glpi-12/tabs/documents.md" class="button secondary">Go to Documents</a>

***

## Links

Links offer several possibilities. Send the GLPI object file to another URL of your choice, or generate an RDP file, for example.

<a href="https://help.glpi-project.org/glpi-12/assets/tabs/links.md" class="button secondary">Go to Links</a>

***

## Notes

Note lets you add enriched text and attach a document.

<a href="broken://pages/XipgLcc0ZI9rHIHkMeM7" class="button secondary">Go to Notes</a>

***

## 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 Information

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.


---

# 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/management/contacts.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.
