> 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/version-management.md).

# Version management

Versions let you update an exam without changing the setup already associated with earlier attempts. You can prepare and preview a new version while the existing one remains available.

{% hint style="info" %}
**Location:** Open an exam, then select **Version management**.
{% endhint %}

### Why exams have versions

An exam can have candidates at different stages while administrators need to correct questions or change settings. Versions prevent every edit from silently rewriting the configuration associated with existing delivery records.

A version tells you which questions and settings a group of attempts used. This matters when you correct a question, change a time limit or compare results before and after an update.

| Concept            | Meaning                                                    | Administrator impact                                            |
| ------------------ | ---------------------------------------------------------- | --------------------------------------------------------------- |
| Current version    | The version currently used for the relevant delivery state | Review its status before changing candidate access              |
| Draft version      | A version being prepared                                   | Changes are not a substitute for publishing or activation       |
| Source version     | The version from which a new version was created           | Use the comparison to understand inherited content and settings |
| Effective settings | The resolved content and configuration for that version    | Check inherited template and global values as well as overrides |
| Student attempts   | Attempts associated with an exam version                   | Creating a new version does not move existing attempts to it    |

### Creating a new version

Before creating a version, identify the reason for the change and which candidates it should affect. Review both question content and exam settings; a new version can contain differences in either area.

1. Record the purpose of the change.
2. Create the new version from the intended source.
3. Update questions, sections and settings.
4. Compare the new version with its source.
5. Preview and quality-assure the complete candidate journey.
6. Activate or schedule the version through the supported workflow.

### Pulling changes from a source

Where an exam is linked to source content or settings, version management can identify newer source changes. Review whether you are pulling content, settings or both. A successful pull does not remove the need to inspect the resulting exam version.

### Closing or cancelling versions

Closing or cancelling a version can affect scheduling and candidate access. The available action depends on the version's state and whether delivery has begun. Check active and scheduled attempts before confirming the change.

{% hint style="warning" %}
Before publishing a new version, note what changed and which students should receive it. Check existing and already-generated attempts rather than assuming they will use the new version.
{% endhint %}

### Check the new version

Preview the complete student experience before publishing. If the version changes timing, marking, results, proctoring or access arrangements, test those areas as well as the questions.


---

# 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/version-management.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.