> 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/collection-details.md).

# Collection details

Collection details give your collection its name, image and description. These are the details students use to recognise the collection and decide whether it is relevant to them.

{% hint style="info" %}
**Location:** Collections → select a collection → Collection details
{% endhint %}

### Fields

| Field                 | What students see                                            | What to enter                                                                                                      |
| --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| **Title**             | Collection lists and the collection header.                  | A clear, specific name such as “GCSE Biology Revision”. This field is required.                                    |
| **Image**             | Collection cards and other supported summaries.              | The editor accepts a landscape image and applies it at card size. Keep essential text out of the image.            |
| **Short description** | A brief summary where space is limited.                      | One or two sentences explaining who the collection is for and what it covers.                                      |
| **Description**       | The fuller introduction shown when the collection is opened. | Use the rich-text editor to explain the content, intended use and any important instructions.                      |
| **Attributes**        | Usually not shown directly to students.                      | Extra fields configured for your portal. Required attributes must be completed before the collection can be saved. |

### Title, short description and description

The three text fields have different jobs:

* **Title** answers “What is this resource?”
* **Short description** helps a student decide whether it is relevant before opening it.
* **Description** can provide the fuller introduction shown after the collection is opened.

In Player view, the description appears as part of the overview unless you skip the overview page. In Cards view, students reach the item cards more directly, so clear item titles and short descriptions become especially important.

### Cover image

The cover image is reused at different display sizes. A simple subject-led image or brand mark is more reliable than a detailed poster. Check the collection at card size after saving; content near the image edges can be cropped or become difficult to read.

### Collection attributes

Attributes are extra fields created for your portal. For example, you might use an attribute to record a subject, qualification level or internal owner. The fields you see depend on how your portal has been configured.

{% hint style="info" %}
Changing an attribute does not automatically change the collection's folders, student access or generated-attempt filters unless your portal has a separate process that uses it.
{% endhint %}

### Clone collection

**Clone collection** creates a separate copy that you can use as a starting point. This is useful when you want a similar collection for a new class or subject without rebuilding its structure. Review the copied details, items, access and settings before sharing it with students.

{% hint style="warning" %}
A clone is not a live variant of the original. Later structural or settings changes do not stay synchronised between the two collections.
{% endhint %}


---

# 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/collection-details.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.