> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/qr.md).

# QR screens

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/qr/README.md).
{% endhint %}

QR forms: reporting a problem or making a request by scanning a QR code, without an account or the app. The form runs as its own small web app (qr\_forms), and a submit creates a task in the form's group.

Signed-in users get a group's codes from [Group QR codes](https://docs.snapfix.com/how-the-apps-work/screens/groups/qr-codes.md), where "Generate QR" makes the group's standard form. Snapfix staff make custom forms in [QR management](https://docs.snapfix.com/how-the-apps-work/screens/staff/qr-management.md). The [QR API](https://docs.snapfix.com/engineering-reference/api/qr.md) covers the form's routes and what a submit creates; the feature is [QR forms](https://docs.snapfix.com/product/features/qr/qr-forms.md).

| Screen                                                                   | Platforms | Where                 |
| ------------------------------------------------------------------------ | --------- | --------------------- |
| [QR form](https://docs.snapfix.com/how-the-apps-work/screens/qr/form.md) | web       | qr.snapfix.com `/:id` |


---

# 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://docs.snapfix.com/how-the-apps-work/screens/qr.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.
