> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/incident-response/fr/readme.md).

# Réponse aux incidents

Localisez les personnes et prenez de leurs nouvelles pendant une urgence

**Aperçu**\
Verkada Incident Response aide les organisations à suivre l’état et la localisation des personnes lors d’une urgence ou d’un incident. Il vous permet de rendre compte rapidement des employés, visiteurs ou élèves et peut être utilisé pour réunir les élèves avec leurs responsables dans les établissements scolaires.

Cette collection explique comment configurer Incident Response dans Verkada Command, notamment l’importation de sites, la gestion des listes de personnel et la création de modèles de réponse qui définissent qui doit être recensé, quels statuts peuvent être utilisés et comment les emplacements sont suivis.

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/incident-response/fr/premiers-pas/incident-response-portal.md">Portail de réponse aux incidents</a></td></tr><tr><td></td><td><a href="/incident-response/fr/configuration/create-response-templates.md">Créer des modèles de réponse</a></td></tr><tr><td></td><td><a href="/incident-response/fr/analyses/review-responses-from-command.md">Examiner les réponses depuis Command</a></td></tr></tbody></table>


---

# 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.verkada.com/incident-response/fr/readme.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.