> 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/tutorials/fr/receivers/receiver_mailbox_delegation.md).

# Collecteur et délégation de boîtes mail

Si votre collecteur utilise une boîte mail déléguée, suivez ces étapes pour la configurer.

!!! Note Ce cas s'applique aux comptes utilisant Azure AD et Gmail

Le principe est de créer votre autorisation depuis le plugin Oauth IMAP sur le compte principal puis, modifier cette autorisation pour identifier le compte délégué. Pour créer le collecteur via un compte Azure, veuillez vous référer à cet article :

[Collecteur avec Oauth IMAP](/tutorials/fr/receivers/oauth_imap_entra.md)

Si votre collecteur est déjà configuré sur le compte principal, suivez ces étapes pour le modifier par la boîte mail déléguée :

* Allez dans **`Setup`** > **`Oauth IMAP applications`** > onglet **`Oauth authorization`** de votre OAuth IMAP
* cliquez sur **`update`**

![Alt text](https://1227510999-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmRzI15ndDbFHGd5BnM4%2Fuploads%2Fgit-blob-6210de59811178f25b4a610892c17259d1c0897a%2Fsharemailbox-1.png?alt=media)

* Saisissez la boîte mail déléguée
* Validez votre modification

![Alt text](https://1227510999-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmRzI15ndDbFHGd5BnM4%2Fuploads%2Fgit-blob-5e13fdd84e39fc60776f7dbd7663dc764206be06%2Fsharemailbox-2.png?alt=media)

![Alt text](https://1227510999-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmRzI15ndDbFHGd5BnM4%2Fuploads%2Fgit-blob-5c022184d4a541e80d4d8c5472da632f2a9bf973%2Fsharemailbox-3.png?alt=media)

* Pour configurer les dossiers du collecteur de la nouvelle boîte, il suffit d'aller dans **`Setup`** > **`receivers`**
* Cliquez sur l'icône qui correspond au dossier que vous souhaitez personnaliser (entrant, archives, etc.)

<div align="left"><img src="https://1227510999-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmRzI15ndDbFHGd5BnM4%2Fuploads%2Fgit-blob-87576668308962e7d29dd625bd2d0b5bef4a43ac%2Fsharemailbox-4.png?alt=media" alt="Alt text"></div>

La liste des dossiers de la boîte mail déléguée apparaîtra

<div align="left"><img src="https://1227510999-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmRzI15ndDbFHGd5BnM4%2Fuploads%2Fgit-blob-6c8bd913ed63e8a335fd2686fe7806c707f08980%2Fsharemailbox-5.png?alt=media" alt="Alt text"></div>


---

# 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.glpi-project.org/tutorials/fr/receivers/receiver_mailbox_delegation.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.
