> 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/reset-qr-codes.md).

# Reset QR Codes

On rare occasions, you may need to reset a user's QR codes.\
For example, if you notice that a QR code is generating an unusually high number of tokens, it could indicate that it was shared with unintended users.

Here is how to proceed:

1. Go to the "**Users"** page.
2. Search for the relevant user and click the three-dot menu at the end of their row.
3. From the drop-down menu, select "**Reset codes",** then confirm in the popup window.

<figure><img src="https://2146493170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJObg1BD3YzyPspvgEySy%2Fuploads%2F4Le3QdQUHXEaIbPeCMab%2FReset%20codes%20EN.jpg?alt=media&amp;token=19cd6f30-5cbc-4d8a-b618-5d90c8692b5a" alt="reset codes" width="185"><figcaption></figcaption></figure>

{% hint style="danger" %}
Please proceed with caution: Once the codes are reset, any previously downloaded or received QR codes will no longer be valid—regardless of the collection. Make sure to inform the user before proceeding.
{% endhint %}

After resetting, you can click "**Send codes"** (from the same drop-down menu) to email the user their new QR codes.


---

# 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/reset-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.
