> 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-senar-studio/collections-accessible-upon-approval.md).
# Collections accessible upon approval
To prevent misuse of your QR codes, you can add an approval level before trainees can access a collection. This can be particularly useful in the case of distance learning sessions.
## How to set approval on a collection
To activate this function, simply check the "**Needs approval**" box next to the collection name.
On the **Collections** page, collections needing approval will display a little padlock in the top right corner:
## Approval Flow
When a student fills out the identification form after scanning the QR code for a collection that requires pre-approval:
* A message will appear on their device, informing them that their access is pending approval from the instructor.
* The instructor will receive an email inviting him/her to approve or deny the student access in SENAR Studio:
* In SENAR Studio, the instructor will grant or deny access by clicking on either the green check or red X button.
* Once the instructor has granted access, an "Access Granted" message will appear on the student's device. The student can then install the simulators of the collection.
* If the instructor denies access, the pending user gets an "Access Denied" message and can't access the simulators. In this case, no token is debited from your account.
{% hint style="info" %}
You cannot withdraw access from a student after you have granted it. But if you have denied access in error, you can reverse your choice ([read more](/using-senar-studio/how-to-resolve-access-denied-in-error.md)).
{% 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-senar-studio/collections-accessible-upon-approval.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.
