> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/tracker-management/tags.md).

# Tracker tags

Group trackers with coloured tags, and share a tag with other RACEMAP accounts.

A tag is a coloured label you put on a set of trackers. Use it to filter the tracker list and to select a group of trackers in one go.

Tags are listed under **Tags** in the tracker management sidebar. The number next to a tag counts the trackers in it that you can see.

Your own tags come first. Tags other users shared with you are listed under **Shared with you**, and tags you shared under **Shared by you**. You can fold either branch. It only appears when there are such tags.

#### How to create a tag and add trackers

* Highlight trackers in the list and click **Tag highlighted trackers**, or click **Add tag**.
* Pick an existing tag, or type a new label and choose **Create tag**.
* To add more trackers later, drag them from the list onto the tag in the sidebar.

Drag a tag into the selection to select all of its trackers.

{% hint style="info" %}
Two tags can have the same label when they belong to different accounts. The sidebar then shows the owner's name next to each label.
{% endhint %}

#### How to share a tag

Click the gear next to a tag to open its settings, then open the **Sharing** tab.

* Search for the account by name or email and add it as **Editor**.
* To remove someone, delete their row.

Sharing a tag does not share its trackers. An editor sees only the trackers they already have access to. The others show as one row, **+N trackers you can't access**. They stay in the tag.

#### What editors can do

| Role        | Permissions                                                                                |
| ----------- | ------------------------------------------------------------------------------------------ |
| **Creator** | Rename and recolour the tag, add and remove trackers, share it, transfer it and delete it. |
| **Editor**  | Rename and recolour the tag, add and remove trackers. Cannot share, transfer or delete it. |

Changes by other users show up the next time you switch back to the browser window.

#### How to transfer a tag

In the **Sharing** tab, give an editor the **Creator** role. You become an editor of the tag and can no longer share or delete it.

#### How to leave a tag

If a tag was shared with you, open its settings, go to the **Sharing** tab and click **Leave tag**. The tag disappears from your list. Its trackers are not changed.

#### How to delete a tag

Only the creator can delete a tag. Open its settings and click **Delete tag**. The tag is removed for you and all editors. The trackers are not changed.


---

# 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://docs.racemap.com/tracker-management/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.