> 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/templates-and-global-defaults.md).

# Templates and global defaults

Templates and global defaults let you reuse the same settings across exams. They save time when you regularly create exams with a similar player, marking process, security setup or results experience.

An exam can use a setting even when you have not chosen it directly on that exam. Before changing a value, check whether you are editing a global default, a template or one exam: the same control can affect very different numbers of exams.

### Inheritance model

Settings can be defined at a global level, in an exam template and on an individual exam. A more specific value can override the inherited value. Resetting a section clears the override so it inherits from the level below.

| Level          | Use                                            | Change impact                                                 |
| -------------- | ---------------------------------------------- | ------------------------------------------------------------- |
| Global default | Your usual setting across the portal           | Can affect many configurations that inherit it                |
| Exam template  | A reusable starting point for one kind of exam | Makes the same group of settings easier to apply consistently |
| Exam override  | A different choice for one exam                | Affects that exam and can differ from the template            |

The interface indicates which attributes are set at the current level. When reviewing an exam, distinguish an explicit value from an inherited one.

### Good template candidates

* standard candidate experience and accessibility tools;
* standard result visibility;
* marking and blind-marking pattern;
* standard legal terms;
* security and proctoring profile;
* usual resit and certificate settings;
* communication defaults.

Schedules usually need dates set for each exam, even when the other settings come from a template.

### Creating a template

Build templates around exam types you use repeatedly, for example “timed remote proctored exam” or “untimed practice assessment.” Avoid creating a separate template for every small variation.

For each template, document:

* owner and approver;
* intended assessment type;
* mandatory versus editable settings;
* supported proctoring/device profile;
* intended result and resit behaviour;
* review date and version history.

### Changing defaults

A global change can be wider than it looks. Before saving:

1. identify which templates and exams inherit the setting;
2. distinguish drafts, unstarted attempts and active delivery;
3. test the new effective configuration on a non-live exam;
4. tell exam owners what has changed;
5. keep a note of the previous value if you may need to explain the change later.

{% hint style="warning" %}
Do not assume that changing a default rewrites historical attempts. Versions and attempt state preserve delivery context, while warnings on some settings identify changes that apply to unstarted attempts.
{% endhint %}

### Exam-specific overrides

An override lets one exam use a different value from its template or the global default. This is useful for genuine exceptions, but too many overrides make the template less helpful. Reset one only after checking what value the exam will inherit instead.

### Keeping templates easy to use

Give each template a clear name and description, limit editing to the people responsible for it, and test it before using it for a live exam. Remove or rename old templates so that admins can easily choose the right one.


---

# 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/templates-and-global-defaults.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.