> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/help/help-center-fr/email-security/google-workspace/permissions.md).

# Autorisations requises

Les champs d'application OAuth autorisés dans la console d'administration Google pendant le [configuration](https://docs.stoik.io/help/help-center-fr/email-security/google-workspace.md). Stoïk ne les utilise que pour analyser les e-mails et les comptes, détecter les menaces et agir rapidement en cas d’incident.

| Autorisation                             | Utilisation                                                                                                                                |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `gmail.readonly`                         | Lire les messages et les paramètres des boîtes aux lettres afin d’analyser les e-mails.                                                    |
| `gmail.modify`                           | Modifier les messages et les libellés dans les boîtes aux lettres (sans suppression définitive), afin d’agir sur les e-mails malveillants. |
| `gmail.insert`                           | Insérer ou importer un message dans une boîte aux lettres uniquement.                                                                      |
| `gmail.metadata`                         | Lire uniquement les en-têtes et les libellés, sans corps ni pièces jointes.                                                                |
| `gmail.settings.basic`                   | Lire et modifier les filtres, la réponse en cas d’absence, ainsi que les paramètres IMAP et POP.                                           |
| `gmail.settings.sharing`                 | Gérer les délégués et les adresses de transfert de courrier.                                                                               |
| `admin.directory.user.readonly`          | Lister les utilisateurs et lire leurs profils d’annuaire.                                                                                  |
| `admin.directory.customer.readonly`      | Lire l’enregistrement client Workspace (nom de l’organisation, domaine principal).                                                         |
| `admin.directory.device.mobile.readonly` | Lister les appareils mobiles gérés et leurs métadonnées.                                                                                   |
| `admin.reports.audit.readonly`           | Lire les journaux d’audit de l’administration (connexions, actions d’administration, activité Gmail).                                      |
| `apps.alerts`                            | Lire, supprimer et donner un retour sur les alertes du Centre d’alerte.                                                                    |


---

# 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://docs.stoik.io/help/help-center-fr/email-security/google-workspace/permissions.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.
