> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/quizzes/creating-a-quiz/quiz-experience/flagging-and-reporting-question-issues.md).
# Flagging and reporting question issues
### Flags
Flags can be enabled from the experience page of quizzes or exams. When enabled users will be able to report and issue from their attempt using the control panel.
When enabled users will be shown a list of reasons as to why they are reporting a question and will be prompted to leave a comment though this can be left blank.
Report an issue / leave a flag button in an attempt
#### Reviewing flags
Admins, Educators or Managers can review flags directly in the question editor. Questions will show with an icon when they have been flagged or reported.
Flags can be viewed in full on each question from the Flags tab and set as resolved which will remove them and show to users that this has been resolved.
Additionally the flags overview can be enabled on the dashboards of admins, educators and managers to give a table view of all the flags per portal / sub portal as well as the option to export and filter by review state.
To enable this dashboard, an admin needs to go to Settings > User Access > Select a type > Dashboard = Enabled > Flags = Enabled
This dashboard can also be enabled for students if you want to give them an overview of only their flags, alternatively students will be able to review their flags on questions in collections if they take another attempt with them in.
---
# 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://synap.ac/docs/quizzes/creating-a-quiz/quiz-experience/flagging-and-reporting-question-issues.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.
