> 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/groups.md).
# Groups
Groups tab allows to add, modify, delete, search groups.
Groups can be defined in a hierarchical structure in order to ease navigation and search.
```
[🏢 Direction / Management]
└── [🏬 IT Division]
└── [🛠️ L3 Support]
└── [🌐 Network]
└── [🔌 LAN]
```
## Practical benefits
1. **Ticket inheritance and visibility**: A technician in the "Network" group will see tickets assigned to the "LAN" child group, whereas a technician in the "LAN" group will not necessarily see tickets from other branches.
2. **Automatic assignment**: It is possible to target a specific team with great precision for hardware assignment (e.g., assigning a switch to the Network > LAN group) or for ticket management rules.
3. **Breadcrumb display**: In a drop-down list or report, the full name "**`L3 Support`** > **`Network`** > **`LAN`**" makes it immediately clear which sub-team is involved, eliminating any risk of confusion.
Groups can be used in several way to group users by:
* **Skills**: for the helpdesk, for example network technicians, or database administrators,
* **Organizational groups**: for example all the computers of the management or the accounting department but also set of persons to be notified.
## Available options
Options are available to adjust these behaviors
Visible in a ticket:
* **Requester**: allows the group to act as requester;
* **Observer**: allows the group to act as observer;
* **Assigned to**: allows the group to be assigned a ticket;
* **Task**: allows the group to be assigned a task;
* **Can be notified**: recipient of notifications;
Visible in a project:
* **Can be manager**: allows [project](/glpi-12/tools/projects.md) management;
Can contain:
* assets
* users.
### Types of groups
In an item form, 2 notions of groups are available:
* [Technical group](/glpi-12/tabs/common_fields/group_in_charge.md) which indicates which group of people is in charge of the asset (equivalent for a group of the technical manager)
* [Group](/glpi-12/tabs/common_fields/group.md) which indicates to which group of items it belongs.
{% hint style="info" %}
The technical group can allow the automatic assignment of a ticket to a group of technicians, see the ticket categories in the chapter [configure dropdowns](/glpi-12/setup/general/assistance.md). Likewise, it can be used in [Business rules for tickets](/glpi-12/administration/rules/ticketbusinessrules.md).
{% endhint %}
{% hint style="success" %}
If all options are set to *No*, the group will not appear in any selection list; this can be useful for a group that is deleted and kept for history or for adding empty groups in the hierarchical structure.
{% endhint %}
### Manager
A group can have one or more managers, concept which can then be used for notifications, for example to send an email to the manager(s) of the group when a ticket is opened, see [notification management](#configure_notifications).
The concepts of manager can be configured in the "Users" tab.
### Delegatee
By default in GLPI, a user opens a ticket for themselves. Group delegation makes it possible to authorize a user to open a ticket on behalf of their group (or a group they are responsible for).
* A practical example: An executive assistant opens an IT ticket for the entire *Accounting* department. Thanks to delegation, the ticket is linked to the *Accounting* group, and all members of the department can track its progress.
### Affectation
Assigning a user o a group is either static and done using the GLPI interface, or dynamic when this is automatically extracted from the LDAP directory.
A group is attached to the entity in which it is created and can then be visible in sub-entities.
### Import
From the list of groups, a group can be imported from a LDAP directory via the *LDAP directory link* button if external authentication is used and the "Auth and sync update" authorization is granted in profile. The assignment of users to groups will be automatic, see [Profiles](/glpi-12/administration/profiles/profiles.md). If several directories are configured, the choice between directories is proposed, otherwise the search form is directly accessible.
Depending on how you search for groups (see [Authenticating users from LDAP directories](/glpi-12/setup/authentication/ldap.md)), a **Search filter in groups** and/or a **User search filter** appear. These allow to refine the list to be imported. If multiple entities exist in GLPI, it is necessary to select the destination entity of the group as well as its visibility in the sub-entities.
{% hint style="info" %}
Importing groups cannot be filtered by entity. In addition, no group synchronization function is available. The only way to refresh from a directory the list of group members is to resynchronize users, see [Import users from an external source](/glpi-12/administration/users/usersimport.md).
{% endhint %}
***
## Import groups
In **`Administration`** > **`Groups`** > **`LDAP directory link`** (at the top of the page), you have the option to import groups. Depending on the settings made, users will be managed dynamically.
Go to Setup LDAP
***
## Child groups
This tab allows to add a subgroup to the selected group and lists the existing subgroups. Each subgroup created will also be visible in **`Administration`** > **`Groups`**
***
## Used items
Tab Used Items tab lists the elements for which the *Group* field corresponds to the current group. The search can be extended to sub-groups as well as to the members of the group (*User* field of the item).
***
## Managed items
Managed Items tab lists the elements for which the *Technical Group* field corresponds to the current group. The search can be extended to sub-groups as well as to the members of the group (*Technical manager* field of the item).
Got to Group in charge
***
## LDAP directory link
This tab only appears if the "Auth and sync update" authorization is granted in profile; it gathers the information allowing GLPI to find the group and its users in the LDAP directory.
***
## Security
In this tab you can force or not the use of 2FA for a specific group
Go to 2FA
***
## Users
This tab allows to add a user to this group by defining whether the added user is *manager* of the group. It also lists the users of this group with possible search by this criteria and also in the subgroups of the current group.
Go to Manage user's group
***
## Notifications
List of notifications for which destination is group or group supervisor
***
## Created tickets
Lists all tickets created by or assigned to the group. If a ticket is created by a group member but the requester is not explicitly the group itself, the ticket will not appear here. Selecting "Show all" displays all created or assigned tickets and redirects you to **`Assistance`** > **`Tickets`**.
Go to Tickets
***
## Created tickets
Tickets references all tickets created by the group.
Go to Tickets
***
## Created probems
Problems references all problems created and assigned to the group.
Go to Problems
***
## Notes
Note lets you add enriched text and attach a document.
Go to Notes
***
## 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/groups.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.
