> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/aphex-help-fr/questions-frequemment-posees/faqs/how-do-i-set-a-reviewer.md).

# Comment définir un réviseur ?

{% hint style="info" %}
**À savoir avant de commencer :**

* Seuls les utilisateurs Admin et Standard du projet peuvent définir des réviseurs
* Les utilisateurs Standard ne peuvent définir des réviseurs que pour eux-mêmes
  {% endhint %}

Définir un utilisateur comme réviseur d’un autre le rend responsable de l’examen et de l’approbation des plans du propriétaire avant la prochaine publication.

Pour définir un réviseur :

* Cliquez sur l’icône Aphex en haut à gauche, au-dessus du diagramme de Gantt
* Ouvrez la **Utilisateurs** page
* Localisez l’utilisateur dont vous souhaitez que les plans soient examinés
* Cliquez sur l’ **+** icône dans la colonne du réviseur
* Sélectionnez l’utilisateur dont vous souhaitez examiner les plans dans la liste déroulante

<figure><img src="https://2817901885-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F78aZmbpbN0t33VMmqiB1%2Fimage.png?alt=media&amp;token=268ca396-085a-473c-97de-3b10ea54c464" alt=""><figcaption></figcaption></figure>


---

# 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.aphex.co/docs/aphex-help-fr/questions-frequemment-posees/faqs/how-do-i-set-a-reviewer.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.