> 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/mdr/management/priority-contacts.md).

# Contacts prioritaires

Définissez vos contacts prioritaires afin que notre équipe puisse vous joindre rapidement lorsqu’une alerte MDR nécessite votre intervention directe.

## Lorsque votre action est requise

Stoïk prend en charge l’analyse et le traitement des alertes de sécurité, mais certaines situations nécessitent votre intervention directe. Par exemple :

* Reformater un poste de travail après une infection confirmée
* Vérification par le SOC : par exemple, si l’utilisateur X utilise un outil Y non répertorié, nous vous demanderons d’en confirmer la légitimité
* Alerte Active Directory : si un compte compromis est détecté, un plan de réponse à incident doit être déclenché selon nos recommandations (mise hors service du réseau, désactivation des comptes VPN, etc.)

## Configuration des contacts prioritaires

Saisissez vos contacts prioritaires dans `Paramètres` > `Utilisateurs`. Pour la configuration complète, consultez [Droits et notifications des utilisateurs](/help/help-center-fr/onboarding/account/users.md#user-rights-and-notifications).


---

# 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/mdr/management/priority-contacts.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.