> 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/documentation/modules/assistance/actors.md).

# Defining actors and roles

An assistance service usually defines the following roles:

* **Requester** : user or group of users known to GLPI and affected by the ticket;
* **Technician**: ticket processing is done by a technician, by a group or by a supplier;
* **Watcher** : user who can follow a ticket but without modifying it; follow-up can be done from GLPI interface or by receiving notifications.

Visible information and possible actions are defined by GLPI based on the user's role, which is defined in user's profile:

* Technicians are the actors having the most complete information on a ticket and the widest possible actions
* Requester and watcher will only view the information needed to fulfill request.

For multiple users or groups, only the first user or group is defined when creating the ticket, more actors are added later. A user who cannot modify actors but able to see the ticket can become a watcher.

When associating a new actor to a ticket, the number of tickets assigned to this actor is visible; this eases for instance task partitioning between technicians.

{% hint style="info" %}

* for users who are not known to GLPI, mail address can be associated to a ticket. Default choice for requester and watcher (no selected user) allows to add a mail address in these fields; for this to be available, notifications must be activated (see [notification management](#configure_notifications))
* Role attribution is done in user's authorization management (see [Attribute authorizations to a user](/documentation/modules/administration/rules/userauthorizations.md))
  {% endhint %}


---

# 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/documentation/modules/assistance/actors.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.