> For the complete documentation index, see [llms.txt](https://support.senar.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senar.io/senar-aide-en-ligne/utiliser-senar-studio/tokens-and-qr-codes.md).

# Tokens & QR Codes

Pour lancer une session de formation qui produira des rapports d'évaluation, les étudiants doivent scanner le QR code d'un utilisateur SENAR actif (Instructeur ou Manager). Ce code permet d'accéder à tous les simulateurs d'une collection.

Lorsqu'un QR code est scanné au sein de l'application SENAR :

* L'étudiant peut installer les simulateurs de la collection sur son mobile (à condition que l'instructeur accepte de lui accorder l'accès).
* L'étudiant peut ensuite utiliser chaque simulateur pendant 5 heures sur une période de 12 mois.
* Un token est débité de la collection sur le compte du client.

Les utilisateurs (Instructeurs et Managers) peuvent télécharger leurs QR Codes - un par collection à la section "**Mon Profil**" de SENAR Studio.

<figure><img src="https://3171608115-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYHnmOLAyCEZ2SwpPQ5NO%2Fuploads%2FajmZMByuFA7IGe1uUlV0%2Ftoken-tracking-x-2-fr.jpg?alt=media&amp;token=c15a1245-8b02-48b4-9efd-bb49bb4ba872" alt="" width="563"><figcaption></figcaption></figure>

Le détail des tokens consommés peut être suivi à la section "**Tokens**".

***

***


---

# 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://support.senar.io/senar-aide-en-ligne/utiliser-senar-studio/tokens-and-qr-codes.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.