> 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/collections/overview.md).

# Overview

Collections bring together quizzes, notes, documents and other Library items in one place for your students. You can use a collection as a set of revision resources, a browsable question bank, a guided learning sequence, or a mixture of all three.

{% hint style="info" %}
**Location:** Collections
{% endhint %}

### What you can create with a collection

A collection lets you decide:

| Area                        | What you can control                                                                                                                      |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Content and structure**   | The Library items in the collection, their order, folders, availability and schedule.                                                     |
| **How students see it**     | Whether students browse cards or move through content in a Player, whether progress is displayed, and which optional tools are available. |
| **Practice and assessment** | Whether students can build their own practice tests, take mocks that you have prepared, and what they see after an attempt.               |

When you add an existing Library item, Synap reuses that item rather than creating a separate copy. If you edit the quiz, note or document itself, the change can appear everywhere it is used. Settings that only apply to this collection—such as its display title, folder, lock status and schedule—remain separate.

### Pages in a collection

| Page                   | What you use it for                                                             | What your students experience                                                         |
| ---------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Collection details** | Set the title, image, descriptions and collection attributes.                   | These details help students recognise the collection and understand what it contains. |
| **Items**              | Add Library items, create folders, arrange the content and configure each item. | Determines what students can open, when it is available and how it is organised.      |
| **User groups**        | Grant groups access to use the collection.                                      | Makes the collection and its permitted items available to members of those groups.    |
| **Configure**          | Choose the layout, progress tracking and optional practice features.            | Determines how the collection is displayed and how students can interact with it.     |
| **Mocks**              | Define named tests generated from the quizzes in the collection.                | Adds a **Generate mock** action with one or more fixed mock options.                  |
| **Access**             | Grant administrative permissions to user groups.                                | Does not by itself give learners access to use the collection.                        |
| **Attempts**           | View historical attempts taken by your students and export the results.         | This is an administrative reporting page and does not change the student experience.  |

### What students see

Students can open a collection from the Collections area or through another part of the portal, such as an assignment. The content and settings stay the same, although the surrounding navigation may be different.

The most important display choice is **Layout**:

* **Cards** makes the collection feel like a browsable library or question bank. Students choose what they want to open.
* **Player** makes the collection feel like a course or guided resource. Students move through an ordered contents menu using **Previous** and **Next**.

See **Cards and Player views** before changing the layout of a collection that is already in use.

### Collection access at a glance

There are two separate types of access:

* **User groups** controls which students can open the collection.
* **Access** controls who can view, edit, manage or delete it as an administrator.

{% hint style="warning" %}
Giving somebody administrative access does not make the collection visible to them as a student. To share the collection with students, add their group on **User groups**.
{% endhint %}

### Collections, courses and exams

| Use                                                                              | Usually choose |
| -------------------------------------------------------------------------------- | -------------- |
| Reusable mixed content or a question bank                                        | **Collection** |
| A managed programme with course-specific progression and completion              | **Course**     |
| A controlled assessment event with scheduling, sittings and operational controls | **Exam**       |

Player view can make a collection feel course-like, but it does not add all of the completion and delivery controls available in a course or exam.


---

# 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/collections/overview.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.
