> 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/platform/exams/access-and-vouchers.md).

# Access and vouchers

Access determines who receives an exam attempt and how they reach it. Registration, user groups and vouchers identify the student; the schedule and Security settings then determine whether they can open it.

These controls answer different questions. Registration decides who should receive an attempt; the schedule decides when it is usable; security decides under which conditions it can open. A candidate can be correctly registered and still be unable to start because a later check is doing its job.

### Registration

| Method              | How candidates are selected                        | Best for                                                      |
| ------------------- | -------------------------------------------------- | ------------------------------------------------------------- |
| User group          | Students come from the group connected to the exam | A class or other group you already manage in Synap            |
| Direct registration | You select individual users on the exam            | A one-off sitting or students drawn from several groups       |
| Voucher             | A student uses a generated code to obtain access   | Purchased access or codes distributed by another organisation |

Registration creates or enrols candidate attempts. With a relative candidate deadline, the registration time also starts the candidate's window.

### Register users

Before registering students:

1. publish the intended version;
2. confirm the schedule and timezone;
3. confirm whether emails are automated;
4. verify access arrangements such as extra time;
5. remove test accounts from the live selection;
6. register a small pilot batch and verify the resulting attempts.

Use bulk registration carefully. A large batch can trigger emails and relative windows at once.

### Exam links

Each authorised attempt can have a direct exam link. The link identifies the route into the assessment; it does not bypass authentication, schedule, lock, passcode, Internet Protocol restriction or proctoring requirements.

When links are exported to an external proctoring system, disable automated registration email if candidates should not receive a separate direct route.

### Vouchers

Vouchers provide controlled exam access through codes. Depending on the configured commerce or registration workflow, they can support purchases, invitations or delegated distribution.

When creating a voucher batch, choose:

* a batch name, which is used as the prefix for its codes;
* how many codes to create, from 1 to 1,000;
* an optional expiry date.

The voucher list shows whether each code is **Pending**, **Redeemed**, **Revoked** or **Expired**. You can revoke or restore selected codes and request a Comma-Separated Values (CSV) export by email. Revoking an unused voucher prevents it being redeemed; check the student’s attempt separately if the voucher has already been used.

Do not place voucher codes in broadly shared documents or public channels. Treat them as access credentials until redeemed or expired.

### Access page

The Access page is the administrative view of who can reach the exam and through which records. Use it alongside Attempt management: Access answers “who is entitled or registered?”, while Attempt management answers “what is happening to each delivery attempt?”

### Removing access

Removing a user from a group does not delete an attempt they already received. Before changing access, check whether the student has started, submitted or received a result.

For a group-based exam, check membership before registration. Adding someone later can create an attempt, start a relative window and send an email, while removing them does not erase the earlier exam record.

### Troubleshooting access

Check blockers in this order:

1. candidate account and portal;
2. registration or voucher redemption;
3. exam and attempt open/close dates;
4. hidden exam versus direct link;
5. lock and passcode state;
6. Internet Protocol allow list;
7. proctoring pre-flight and device requirements;
8. attempt status, including submitted or expired.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://synap.ac/docs/platform/exams/access-and-vouchers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.