> 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/administration/users/users.md).
# Users
The Users tab allows you to manage their information (mail, name, authorization, etc.).
{% hint style="warning" %}
Some information may not be editable depending on how the user was imported. For example, the email address of a user imported from an LDAP(S) cannot be modified.
{% endhint %}
{% hint style="success" %}
You can import users. You can refer to [import users](/glpi-12/administration/users/usersimport.md)
{% endhint %}
It is possible to deactivate a user if needed. If deactivated, the user can no longer be selected in drop-down menu for tickets or inventories, but keeps associated items and tickets. Validity dates can also define the activity time slot of user: the user account will be considered as active only after the start date and/or before the end date. Both dates can be defined independently.
A photo can be added manually or imported automatically from a directory (see [Authenticate users with LDAP](/glpi-12/setup/authentication/ldap.md)).
***
## Impersonate
For debugging or administrative purposes, it's possible for a "super-admin" account (or any profile with the configuration rights) to temporarily take the ownership of another user's account without knowing its password. An icon is available at the top of the user´s form to perform this action.
To note:
* A special banner will show permanently as long as the function is active and will allow you to exit this mode.
* After the exit, the user will retrieve its session as it was before using the feature.
* The history of actions taken by the administrator will appear with a special note: "user (xxx) impersonated by admin (yyy)".
{% hint style="warning" %}
Impertonate allows users whose current profile is higher or equally privileged as every profile of the other user. For example, a technician with this right could impersonation self-service users but not admins. This is mainly to avoid privilege escalation.
{% endhint %}
***
## Vcard
You can download a user vcard by this icon :
In a display form, the following information is available:
### User Information
* **Login**\* : Used to log in to GLPI.
* **Surname**\*
* **Firstname**
* **Timezone**: by default "*use server configuration*". If timezone are not active, go to [timezone](https://glpi-install.readthedocs.io/en/latest/timezones.md#timezones)
* **Active**
* **Valid since**
* **Valid until**
* **Authentication**\* : Indicates the authentication source (internal database, LDAP or other)
* **Category**
* **Title**
* **Comments**
* **Administrative number**
* **Location**
* **Default profile**
* **Default entity**
* **Default group**
* **Supervisor**
### Contact information
* **Emails**\*
* **Phone**
* **Mobile phone**
* **Phone2**
### Password and access keys
* **API token**
* **Password**
(\*) If the user was imported by a provider (LDAP, SCIM, etc.), this information cannot be modified manually.
***
## Authorizations
This tab allows to manage user authorizations. A summary tab displays already attributed authorizations for the user.
Go to Authorizations
***
## Groups
This tab lists the groups associated to the user. Table includes group name, whether the group is dynamic (i.e. linked to a directory service), whether the user is delegatee or manager for the group.
If modify user authorization is granted, it is also possible from this tab to assign a group to the user.
Go to Groups
***
## Settings
This tab allows to edit user's settings. In order to be able to modify data in this tab, general configuration modification authorization must be granted.
Information modified from this tab takes priority over the [general configuration](/glpi-12/setup/general/default_values.md) of glpi
Go to Preferences
***
## Used items
Used items lists the items for which user is defined in field *User* of the item (computer, monitor, peripheral, etc.) por for which user is member of the group defined in field *Group* of the item.
***
## Managed items
Managed items lists the items for which user is defined in field *Technician in Charge* of the item or for which user is member of the group defined in field *Group in Charge* of the item.
Go to Techncian in charge
***
## Consumables
Consumables lists all items assigned to the user.
Go to Consumables
***
## Created tickets
Tickets references all tickets created by the user.
Go to Tickets
***
## Created probems
Problems references all problems created and assigned to the user.
Go to Problems
***
## Created changes
Changes references all changes created and assigned to the user.
Go to Changes
***
## 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.
Go to Documents
***
## Reservations
This tab lists passed, current and future reservations of the user. In order to see this tab, read authorization on reservation management must be granted.
Go to Reservations
***
## Synchronization
This tab is displayed if *Update Authentication and Synchronization* right is granted. It allows to change authentication method for the user and to force its synchronization.
***
## Links
Links offer several possibilities. Send the GLPI object file to another URL of your choice, or generate an RDP file, for example.
Go to Links
***
## Certificates
Link a certificate to your registration. You can manage certificates in **`Management`** > **`Certificates`**
Go to Certificates
***
## Licenses
Licenses play an important role in managing the software used in an organisation. They make it possible to manage software usage rights, to know who is using a license, how many are available and how many are being used. GLPI makes it possible to associate costs with licenses, which facilitates budget management. Licenses can be linked to equipment (computers, servers, etc.) or to specific users, so you know who is using what. It is also possible to set up expiry alerts.
Here are the fields available from this tab:
* Name
* Serial number
* Number
* Affected Items
* Type
* Purchase version
* Version in use
* Expiration
* Status
Go to Licenses
***
## Contracts
GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...
Contracts management allows to:
* make an inventory of all contracts related to the organization assets
* integrate contracts in GLPI financial management
* anticipate and follow contract renewal.
* Documents
The [document](/glpi-12/management/documents.md) 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.
Go to Contacts
***
## 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 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/glpi-12/administration/users/users.md?ask=&goal=
```
`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.