> 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/using-the-senar-app-and-ar-simulators/setting-up-devices-to-use-senar-in-the-classroom.md).
# Setting up devices to use SENAR in the classroom
1. Make sure that each device is charged and running the latest version of the SENAR application.
2. Exit the current training session in between students. To do so:
a. Open the **Menu** by tapping the Profile icon at the top left corner of the Library.
b. Tap the "**Sign out**" button then confirm Exit in the popup window.
{% hint style="warning" %}
It is key for each student to start their own session, by scanning your collection QR code and filling out their own identification form. Otherwise, the Analytics reports won't be usable.
{% endhint %}
3. If you don't have it yet, download your collection QR code from the "My profile" section in [SENAR Studio.](https://studio.senar.io/) It will be ready to be scanned by your students.
{% hint style="info" %}
We recommend that you quit and restart SENAR every day as the application checks for simulator updates at each launch. Note that quitting the application does not interrupt the current training session.
{% endhint %}
---
# 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/using-the-senar-app-and-ar-simulators/setting-up-devices-to-use-senar-in-the-classroom.md?ask=&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.
