> 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-nl/email-security/google-workspace/permissions.md).

# Vereiste machtigingen

De OAuth-scope(s) die zijn geautoriseerd in de Google Admin-console tijdens de [instelling](https://docs.stoik.io/help/help-nl/email-security/google-workspace.md). Stoïk gebruikt ze alleen om e-mails en accounts te analyseren, bedreigingen te detecteren en snel te handelen in geval van een incident.

| Machtiging                               | Gebruik                                                                                                                         |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| `gmail.readonly`                         | Berichten en instellingen in de postvakken lezen om e-mails te analyseren.                                                      |
| `gmail.modify`                           | Berichten en labels in de postvakken wijzigen (geen permanente verwijdering) om actie te ondernemen tegen kwaadaardige e-mails. |
| `gmail.insert`                           | Alleen een bericht in een postvak invoegen of importeren.                                                                       |
| `gmail.metadata`                         | Alleen headers en labels lezen, zonder inhoud en bijlagen.                                                                      |
| `gmail.settings.basic`                   | Filters, vakantieantwoord, IMAP- en POP-instellingen lezen en wijzigen.                                                         |
| `gmail.settings.sharing`                 | Gedelegeerden en e-maildoorstuuradressen beheren.                                                                               |
| `admin.directory.user.readonly`          | Gebruikers weergeven en hun directoryprofielen lezen.                                                                           |
| `admin.directory.customer.readonly`      | Het Workspace-klantrecord lezen (organisatienaam, primair domein).                                                              |
| `admin.directory.device.mobile.readonly` | Beheerde mobiele apparaten en hun metagegevens weergeven.                                                                       |
| `admin.reports.audit.readonly`           | De controlelogboeken van de beheerder lezen (aanmeldingen, beheerderacties, Gmail-activiteit).                                  |
| `apps.alerts`                            | Waarschuwingen in het Alert Center lezen, verwijderen en er feedback op geven.                                                  |


---

# 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-nl/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.
