# Assistance tab

## Assistance permissions

### Simplified interface

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FkIW1IZ5IQ1bfiIFCnGX5%2Fauthorizations_assistance_self_service.png?alt=media&#x26;token=e5ecb548-2621-40dd-978e-4037ca5f6630" alt="../images/assistancePO.png"><figcaption></figcaption></figure>

**Default ticket templates**: default templates for Tickets, Changes and Problems that will apply for profile.

{% hint style="info" %}
The template being applied to the profile which is an element of the general configuration, the list contains only the recursive templates of the root entity.
{% endhint %}

#### Tickets permissions

* **See My Ticket**: see all the tickets for which I am the writer, the requester or the observer as well as their public follow-ups;
* **Create**: adds a **Create Ticket** menu. If you do not have this permission, when you log in, you will be directed to the list of tickets. Otherwise, you will be redirected to the home page which displays my tickets, sorted by status, with the **Create ticket** menu as the table title;
* **See Group Ticket**: see the tickets created which have one of my groups as an requester or observer. For example, if I am a member of the *Management* group, I will see all the tickets having a requester in group *Management*.

#### Followup permissions

* **See Public Ones**: see all followups typed as public followups;
* **Update followups (author)**: modify the follow-ups you have created;
* **Add followup (requester)**: add a follow-up to a ticket for which I am a writer or requester. This right also allows you to add a document to a ticket;
* **Add followup (associated groups)**: add a follow-up to a ticket for which the requesting group is one of the groups of which I am a member;
* **Add observer/technicien**: allow the user to add an observer or assign them to a technician directly.

#### Tasks permissions

* **See Public Ones**: see all the tasks typed as a public task. This right also allows the display of the *Tasks* tab of a ticket.

#### Ticket approvals

* **Create for request**: send a validation request for a request type ticket;
* **Create for incident**: send a validation request for a n incident type ticket;
* **Approve a request**: respond to a validation request concerning a Request type ticket. Having this right makes you appear in the list of people who can validate.
* **Approve an incident**: respond to a validation request concerning an Incident type ticket. Having this right makes you appear in the list of people who can validate.

The *Validation* tab will only appear in the ticket if you have one of the validation creation permission. Otherwise, it will only be displayed if you have one of the validation permissions and only if the type of the ticket corresponds to the permission.

#### Mentions configuration

This option allows users to mention people in their tickets/follow-ups.

{% hint style="warning" %}
Please note that this right is also restricted at the entity level. A person from entity A cannot mention another user from entity B if the two entities do not allow recursion.
{% endhint %}

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FKj6ReSv2okRsS11VKiYM%2Fauthorization_mention.png?alt=media&#x26;token=c28fe49b-7fa6-41a7-ad8d-e5e05aae45ec" alt=""><figcaption></figcaption></figure>

#### Associations permissions

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FjHmxBUcGG91Jxd8NbtBf%2Fauthorization_association.png?alt=media&#x26;token=471fb61f-62fd-4927-a70f-08d8a636c971" alt="../images/associations.png"><figcaption><p>Associations permissions</p></figcaption></figure>

* **See hardware of my groups**: asset whose type is authorized and for which I am a member of the group;
* **Link with items for the creation of tickets**:
  * **My Devices**: assets whose type is authorized and for which I am the user;
  * **All Items**: all assets of my entity whose type is authorized.
* **Associable items to a ticket**: types of asset on which a ticket can be associated. To add a type, just click in the white area and choose the authorized type or *All* if you want to authorize all types. To delete a type, simply click on the cross to the left of its name or on *None* if you do not want to allow any associated element

<details>

<summary>Authorised items</summary>

* Computers
* Monitors
* Network devices
* Peripherals
* Phones
* Printers
* Software
* Licences
* Certificates
* Lines
* Server rooms
* Racks
* Enclosures
* Clusters
* PDUs
* Domains
* Domaines records
* Appliances
* Simcard
* Passive devices
* Database instances
* Databases
* Cables

{% hint style="info" %}
If you create elements using asset definitions, they will also appear in the list.
{% endhint %}

</details>

### Standard interface

Common fields with the simplified interface will not be detailed. The 7 standard permissions will not be listed (see [Permissions description](https://help.glpi-project.org/documentation/modules/administration/profiles/profiles)).

#### Template & ITIL Objects

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FHZN6frlfr0xRDq7XcsTp%2Fauthroization_ticket_standard_interface.png?alt=media&#x26;token=1dec6b6b-a2ec-4594-a186-4fe3939c52f8" alt="../images/assistance_general.png"><figcaption><p>Default ITIL templates</p></figcaption></figure>

* **Default ITIL templates**: default templates for Tickets, Changes and Problems that will apply for profile;

{% hint style="info" %}
The template being applied to the profile which is an element of the general configuration, the list contains only the recursive templates of the root entity.
{% endhint %}

* **Templates**: manage ticket/change/problem templates;
* **Pending reasons**: manage pending reasons.

#### Tickets permissions

This section also includes **costs** related to tickets and **recurrent tickets**.

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2F9EQRWDowo12hZEHBkaMH%2Fauthroization_ticket_standard_interface.png?alt=media&#x26;token=3cf5fea6-862b-4574-87d1-2f3336c824a4" alt="../images/tickets.png"><figcaption><p>Tickets permissions</p></figcaption></figure>

* **See my tickets:** ticket that I have requested or that has been assigned to me;
* **See All tickets**: see all tickets created in the entity;
* **See group ticket**: see all tickets assigned to my group(s);
* **See Assigned**: see tickets for which I am the technician or having one of my groups as group of technicians;
* **Assign**: add a technician, a group of technicians or a supplier to a ticket;
* **Steal**: become the technician assigned to the ticket. In this case, the list of technicians who can be assigned to the ticket will only include the name of the person connected;
* **Be in charge**: be assigned to a ticket. All the users of this profile having this option enabled will be present in the list of technicians who can be assigned to a ticket. This option also allows users with this profile to update certain fields in the tickets assigned to them, even if they do not have update permissions;
* **Change the Priority**: change the priority in order to make an incident a Major priority, among other things. Modifying the priority therefore cancels the automatic calculation defined in the general configuration.
* **Approve solution/reply survey (my ticket)**: allows you to approve a solution or accept or reject a satisfaction survey
* **View new tickets**:

Starting with GLPI 11, it is now possible to define whether or not a profile can view tickets with the New status.<br>

On the tickets page, users will see all tickets that concern them, i.e.:

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FfgeJSdFKdAMEkwpGwCo9%2Fauthorization_view_new.png?alt=media&#x26;token=ff99bf69-4322-4bc4-84fc-068372b3f635" alt=""><figcaption><p>Profile with the right to view new tickets</p></figcaption></figure>

* Tickets assigned directly to them;
* Or those assigned to their groups;
* As well as tickets with the status new.

Once this option is disabled, all users with this profile will only see tickets that concern them. Tickets with the status “new” will therefore no longer be visible

**Special cases :**<br>

1. **My user is involved in a new ticket**

If my user is involved in an incoming ticket (as a *Requester*, *Observer* or *Technician*), it will remain visible to them, even if the **View new tickets** option is disabled.<br>

2. **My user's profile has the right to "View all tickets"**

The **View all tickets** option takes precedence over the **View new tickets** option. This means that if **View all tickets** is enabled, the user will continue to see *New* tickets, even if the **View new tickets** option is disabled.

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FieBHpeiaW0eJ3rk7CAuU%2Fauthorization_all_no_new.png?alt=media&#x26;token=44a60137-b25b-40f3-9cf3-3d2362917736" alt=""><figcaption><p>Profile with the right to ‘View all tickets’ and without the right to ‘View new tickets’</p></figcaption></figure>

All tickets are therefore visible to the user. The fact that the ‘View new tickets’ right is disabled is not taken into account.

#### Problems permissions

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FGwKnET5IvNqvZJ644oI0%2Fauthorizations_problems.png?alt=media&#x26;token=b0a0523f-a007-4a2e-a585-3d808b819cb5" alt="../images/problems.png"><figcaption><p>Problems permissions</p></figcaption></figure>

* **See (author)**: view problems for which I am a requester, or a member of the requesting group, or an observer, or a member of the observer group, or the assigned technician, or member of the assigned group.
* **See All**: see all the data of a problem.

#### Changes permissions

This part also includes **validations** and **recurrent changes**

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Ffik1mqvq0w7sfnkFcibp%2Fauthorizations_changes.png?alt=media&#x26;token=93c6537a-692a-4136-9346-ff05fb25d3b8" alt="../images/changes.png"><figcaption><p>Changes permissions</p></figcaption></figure>

* **See (author)**: see the changes for which I am the requester, or member of the requesting group, or observer, or member of the observer group, or the assigned technician, or member of the assigned group.
* **Reply to survey (my change)**: allow me to respond to a satisfaction survey regarding the changes I have requested

#### Followups permissions

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FpwbTBcENvx1txQAnC5j7%2Fauthorizations_followup.png?alt=media&#x26;token=dfba818e-8f75-4d97-a1a5-fd53773c7355" alt="../images/followups_and_tasks.png"><figcaption><p>Followups permissions</p></figcaption></figure>

* **See Private Ones**: see all followups typed as private follow-up.
* **Update All**: modify all followups, regardless of the author.

{% hint style="info" %}
A technician assigned to a ticket or member of the assigned group, can also modify all follow-ups.
{% endhint %}

* **Add to all items**: add a follow-up to all items of the entity;
* **See Private Ones**: see all the follwups/tasks typed as private;
* **Update All**: modify all tasks, regardless of the author;
* **Add (associated groups)**: Add groups to ticket task.

{% hint style="info" %}
A technician assigned to a ticket or member of the assigned group, can also modify all tasks.
{% endhint %}

* **Add to all tickets**: add a task to all tickets of the entity.

#### **Mentions**

See [mentions ](#mentions-configuration)for more details

#### Approvals permission:

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2F66CBSsd0rrYXKPT1tg74%2Fauthorizations_approvals.png?alt=media&#x26;token=abb8ecb7-1dd3-44ff-9e19-35117abc5705" alt=""><figcaption></figcaption></figure>

* **Create**: send an approval request
* **Purge**: delete an approval request
* **Validate**: respond to an approval request. Having this right makes you appear in the list of people who can validate.

The *Approvals* tab will only be displayed in the ticket if you have one of the *Validation* permissions.

#### Assocation permissions

See [Association ](#associations-permissions)for more details

#### Visiblity and planing permissions

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Fwzk9IKpO6H7CFJf5q8SA%2Fauthorizations_permissions.png?alt=media&#x26;token=0aeab01c-fac3-4140-a36b-5f2dbaab4dd3" alt="../images/planning_visibility.png"><figcaption><p>Planning visibility permissions</p></figcaption></figure>

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2F9B0HWORLz1flw18iAqwq%2Fauthorization_planing.png?alt=media&#x26;token=366c2a87-06c4-4d64-845a-41c37190ad3b" alt="../images/planning.png"><figcaption><p>Planning permissions</p></figcaption></figure>

* **See personal planning**: only see my planning data.
* **See all plannings**: see the data of all plannings
* **See schedule of people in my groups**: see the data of the plannings of the members of my groups.

Depending on the permissions of the profile, you can see the notes published in the planning as well as the tasks of a ticket, a problem or a change.


---

# Agent Instructions: 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:

```
GET https://help.glpi-project.org/documentation/modules/administration/profiles/assistancetab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.