> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/exams/create-and-manage-exams/marking/moderator-only-marking-simple-marking.md). # Moderator only marking - Simple marking Learn how to set up and use moderating marking on your Synap exams {% hint style="info" %} Key points * Moderating markers can provide the complete and final set of marks for an attempt. * If there are multiple moderating markers working on an attempt **it is the first moderating marker to complete and submit a full set of marks** for an attempt will be used as the final complete set of marks and feedback. * Any Marker, Educator, Manager or Admin needs to be in the moderating marker list for each exam. * Only questions that are not automatically marked by the system can be marked * A moderating marker needs to mark all question in an attempt before they can submit their marks (even if they split their marking by question instead of candidate) {% endhint %}
### Configure moderating only marking On your exam, go to the marking page. From here you'll need to add individual users or groups to the moderating markers list. Users can be added or removed after the exam is published
Set the type of allocation you want, this is how markers are assigned to attempts ready and eligible to be marked: * **Round robin:** Markers are assigned automatically by the system. Marker capacity is taken into consideration during the assignment. Select this method if you don't want to manually assign all attempts to specific markers * **Manual allocation**: Markers must be assigned by an admin or other user with the correct permissions from the attempt management table, or through the API. Select the Blind marking configurations
* **Candidate concealment**: Moderating markers will not know who's attempt they are marking * **Marker concealment:** Is more releavant if you're using additional roles. For Moderating marking only even if there are multiple moderating markers, marking an attempt at the same time, they won't be able to see each others input nor information about the other markers {% hint style="warning" %} Candidate concealment configurations do not apply to admins, educators or managers who have permissions to access attempts outside of being assigned as a marker. {% endhint %} Save the marking set up and publish the exam, once attempts are submitted they will be assigned to markers (round robin) or become eligible to be marked. ### Marking attempts Moderating markers who are only the marker user type, can navigate to the markers inbox page, for Admins, Managers, Educators this page can be enabled or they can mark from the attempt management table (more below). The markers inbox gives each marker an overview of all attempts assigned to them specifically. The inbox is easy to use and navigate, there is a tab for all the open attempts and a tab for all the completed attempts. Markers can search for attempts by id or exam name, and by default the inbox is ordered by attempt submission, showing the longest waiting first. {% hint style="warning" %} 📍Markers who are only of the user type Marker will only have the markers inbox page enabled. No other pages are available to add for users of this type. If markers are also admins, educators or mangers you may need to enable the markers inbox from your portal settings for that user type. {% endhint %}

Navigating the markers inbox

{% content-ref url="/pages/QaETZla02hHTj0bkLRML" %} [6. Manage](/doc/exams/create-and-manage-exams/6.-manage.md) {% endcontent-ref %} {% content-ref url="/pages/LmqcA1xrPgV5mHSzIC6f" %} [Mark/Score attempts](/doc/exams/mark-score-attempts.md) {% endcontent-ref %} --- # 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://academy.synap.ac/doc/exams/create-and-manage-exams/marking/moderator-only-marking-simple-marking.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.