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

# Overview

Advanced features appear throughout Synap rather than belonging to one page or content type. This section explains the shared rules once, so you can recognise the same feature when it appears on users, content, assignments, exams or results.

These features are optional building blocks. A small team can run a portal successfully without configuring all of them. Introduce them when they solve a clear problem, and test the result with both an administrator and a student account.

**In this section**

* **Dynamic content** — personalise text using variables, conditions, fallbacks and repeating content.
* **Attributes** — add structured fields to users, content, attempts and other records.
* **Tags and facets** — classify questions for search, selection, learner practice and reporting.
* **Access and permissions** — control which staff can manage particular areas and records. Student access is handled separately through delivery and enrolment controls.

**How the features fit together**

| If you want to…                                                   | Use                        | Example                                                                          |
| ----------------------------------------------------------------- | -------------------------- | -------------------------------------------------------------------------------- |
| Personalise wording or show different content in a rich-text area | **Dynamic content**        | Address a student by name or show different instructions after a pass and a fail |
| Store an extra, structured value against a Synap record           | **Attributes**             | Add a student number to users or an awarding body to exams                       |
| Classify questions and build reusable filters                     | **Tags and facets**        | Organise questions by subject, topic and difficulty                              |
| Decide which staff teams can view or change an area               | **Access and permissions** | Let one educator group edit a particular quiz bank                               |

Attributes and tags can look similar, but serve different purposes. An attribute describes one record; a tag classifies content against a shared taxonomy. Permissions govern staff capabilities; they do not enrol students onto learning.

**A safe way to introduce an advanced feature**

1. Write down the problem it should solve and the records or people it affects.
2. Configure it in a sandbox or on a small test set.
3. Check both the administrator view and the resulting student experience.
4. Test imports, exports, reports and integrations that depend on the affected data.
5. Record the owner and naming convention before rolling it out more widely.

{% hint style="info" %}
You do not need these features to create your first content. Return here when you need personalisation, organisation-specific data, structured question classification or more granular staff access.
{% 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/advanced-features/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.