> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/portal-settings/data-management/tag-manager.md).

# Tag manager

New tags will automatically be created and stored in the tag manager, or you can create tags first by going to **Settings > Pages > Add Tag.** From the tag manager you can find the tag ID and label. You'll need the label to add tags to a spreadsheet or to questions in the builder. This is also where you'll assign facets to different tags

![](https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2FOyguKu6QpaJ4ksEEQFaI%2FScreenshot%202022-01-10%20at%2016.23.13.png?alt=media\&token=b278682c-f88d-4483-a9df-14e676f4d4d9)

#### 📇 Labels

Capitals and spaces are accepted in tag label names. We recommend you keep the labels as short as possible so they display well on mixed screen sizes.

Tags are case sensitive so its important that when adding tags, that the same tag has the same capitalisation rules.  For example, if some maths questions are tagged as 'Maths' and some as 'maths' then these will be two separate tags. &#x20;

To make this process easier and more reliable we recommend creating the tags via the Tag manager rather than by quiz builder.

#### 👀 Visibility

New tags are visible to students by default. However, you may want to have tags that aren't visible to students. Change the visibility of a tag via the tag manager and tag editor. <mark style="background-color:yellow;">Note that faceted tags must be visible to students</mark>&#x20;

If a tag is faceted and you want to hide it from students, the facet must be removed first in order to update the visibility.

![Setting labels and visibility settings in the tag manager ](https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2FkxI2kHQ7rOVkhKqkqJeB%2FScreenshot%202022-01-10%20at%2016.26.38.png?alt=media\&token=329a3b3e-8c40-4cfe-9297-63177581b964)

### 📚  Facets

From the tag manager you can assign different facets to different tags. Choose from the following :&#x20;

* **Content :** The content hierarchy looks like **Exam>Module>Subject>Topic>Subtopic**
* **Skill**
* **Difficulty**&#x20;

![Facet selector ](https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2FjQlhADYzv0ZDCmSf6ae9%2FScreenshot%202022-01-10%20at%2016.31.00.png?alt=media\&token=a1da3d4b-4f1d-417e-8c19-f4a9d7357f2a)

Please see our facet best practices for more information and guidance on how to select facets for your tags. Use the chat on platform to talk to an account manager who will make suggestions about how to order and facet your content&#x20;

{% content-ref url="/pages/2nc56hN8WuQgPO3sSVP7" %}
[Facet best practice](/doc/analytics/tags-and-facets/facet-best-practice.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.synap.ac/doc/portal-settings/data-management/tag-manager.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
