> 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/human-security/advanced/score.md).

# score de sécurité de l’employé

Chaque employé reçoit un score de 0 à 100, mis à jour chaque jour. Il reflète la façon dont il réagit face à une menace, sur la base de trois signaux :

* **Simulations :** la manière dont ils réagissent aux simulations qu’ils reçoivent. Ignorer un e-mail de phishing rapporte un score élevé, soumettre des identifiants rapporte zéro.
* **Formation :** les leçons qu’ils terminent, et le nombre de tentatives que cela leur prend.
* **Signalement :** un bonus pour les employés qui signalent des e-mails suspects avec le [bouton Signaler](https://docs.stoik.io/help/help-center-fr/human-security/report-button.md).

Il n’y a rien à configurer. Pour voir les scores, allez à `Aperçu` > `Équipe`.

## Bandes

| Niveau       | Signification                                                    |
| ------------ | ---------------------------------------------------------------- |
| **Fiable**   | Gère systématiquement les menaces correctement                   |
| **Modéré**   | Globalement correct, quelques écarts occasionnels                |
| **Faible**   | Se laisse régulièrement piéger par les simulations ou les ignore |
| **Critique** | Risque le plus élevé, a généralement soumis ses identifiants     |

Les bandes définissent également la fréquence des rappels de [rappels basés sur le comportement](https://docs.stoik.io/help/help-center-fr/human-security/advanced/reminders.md).


---

# 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/human-security/advanced/score.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.
