> 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/receivers/receiver_mailbox_delegation.md).
# Receiver and delegating mailboxes
If your receiver uses delegated mailbox, follow these steps to configure it.
!!! Info This case applies to accounts using Azure AD and Gmail
The principle is to create your authorization from Oauth IMAP plugin on the main account and then, modify this authorization to identify the delegated account. To create the receiver via an Azure account, please refer to this article :
[Receiver with Oauth IMAP](/receivers/oauth_imap_entra.md)
If your receiver is already configurated on the main account, follow these steps to modify it by the delegated mailbox :
* Go to **`Setup`** > **`Oauth IMAP applications`** > **`Oauth authorization`** tab of your OAuth IMAP
* click on **`update`**
* Enter the delegated mailbox
* Valid your modification
* To configure the folders of the receiver of the new box, you just have to go to **`Setup`** > **`receivers`**
* Click on the icon that corresponds to the folder that you waant to customize (incoming, archives, etc.)
The list of the delegated mailbox's folders will appear
---
# 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/receivers/receiver_mailbox_delegation.md?ask=&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.
