> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigilyze/settings-and-customisation/create-and-manage-tags.md).

# Create and manage tags

Tags help organisations structure and prioritise investigations. They can be used to support workflows, identify responsibilities, indicate priorities or organise investigations according to local procedures.

Tags are available to all users within the organisation.

 

Examples include:

* Priority: High, Medium, Low
* Team: Signal Detection, Signal Assessment
* Product area
* Review status
* Project name

A specific tag belongs to a tag groups depending how it was set up.

#### What is a tag group?

A tag group is a list of related tags.

For example:

**Priority**: High, Medium, Low

or

**Review type**: Routine review, Rapid review, Literature review

Organising tags into groups helps support consistent use across the organisation.

### Reorder tag groups and tags

Tag groups and tags can be reordered to match your organisation's preferred workflow.

To reorder items:

1. Open **Tag list** .
2. Drag and drop the tag group or tag to a new position.
3. Changes are saved automatically.

The new order becomes visible to all users within the organisation.


---

# 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://support.who-umc.org/vigilyze/settings-and-customisation/create-and-manage-tags.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.