> 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/verkada-cameras/fr/configuration/view-and-edit-camera-settings/camera-notes.md).

# Notes de la caméra

Documentez et recherchez les informations importantes liées à vos caméras

Les notes vous permettent d’ajouter et d’organiser des informations pour les caméras. Les notes peuvent être utilisées pour suivre les points d’installation des appareils, les demandes de maintenance, les plannings de nettoyage, etc. Vous pouvez rechercher des caméras par leurs notes et afficher ces notes comme une colonne sur la page Appareils.

***

## Créer des notes de caméra

{% hint style="danger" %}
Vous devez [Administrateur du site](/command/fr/utilisateurs-et-autorisations/roles-and-permissions-for-command.md) autorisations pour créer des notes de caméra.
{% endhint %}

{% stepper %}
{% step %}
**Dans Verkada Command, accédez à Tous les produits > Caméras.**
{% endstep %}

{% step %}
**Sélectionnez la caméra que vous souhaitez configurer.**
{% endstep %}

{% step %}
**En bas à droite, cliquez sur Paramètres.**
{% endstep %}

{% step %}
**Sous Général > Notes, ajoutez la note de caméra.**
{% endstep %}
{% endstepper %}


---

# 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/verkada-cameras/fr/configuration/view-and-edit-camera-settings/camera-notes.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.