> For the complete documentation index, see [llms.txt](https://swu-forge.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swu-forge.gitbook.io/docs/decks/managing-decks/tagging-decks.md).

# Tagging Decks

Tags are colored labels you attach to decks for fast organization and filtering. Think of them as cross-folder groupings — a deck can live in any folder and still be tagged "Aggro" or "Tournament Top 8" or whatever scheme makes sense to you.

## Personal vs Team Tags

There are two kinds of tags, with different visibility:

* **Personal tags** are owned by you. Only you can see and apply them, and they only attach to decks you own.
* **Team tags** are owned by a team you belong to. Every member of that team sees the same set of team tags, and any team member with EDITOR access or higher can create, rename, delete, or apply them. VIEWERs see team tags on decks they can read, but can't manage them.

In every place tags appear (filter chips, the manage modal, the deck detail header), team tags carry a small badge with the team's photo (or its first initial if no photo is set). Personal tags have no badge.

## Creating Tags

From **My Decks**, click **Manage tags** at the right of the tag filter row (or **+ Create your first tag** if you don't have any yet). The modal opens with a **Personal** section plus one section per team you belong to.

In any section you can manage:

* **+ New tag** — adds a tag to that section. Pick a name (up to 24 characters) and one of 8 colors.
* **Rename** — click an existing tag's name to edit it inline.
* **Recolor** — click the color swatch on the left of a tag's row to pick a different color from the palette.
* **Delete** — the × button removes the tag from every deck it was applied to. A confirmation shows the affected deck count first.

Tag names are unique within an owner (case-insensitive), so you can have a personal "aggro" *and* a team "Aggro" at the same time, but you can't have two personal tags named "aggro".

## Applying Tags to a Deck

There are two ways:

1. **From the deck detail page** — Tag pills appear at the top of the deck header next to the format/card-count pills. Click **Edit tags** (or **+ Add tags** if none are applied yet) to open the modal in *deck mode*. The top of the modal shows an apply panel: every tag you're allowed to apply to this deck appears as a pill. Click a pill to apply or remove — filled = applied, outlined = not.
2. **From My Decks** — Open the more-actions (⋮) menu on any deck row and choose **Edit tags**. Same modal, same apply panel, scoped to that deck.

Each deck can hold up to 10 tags.

## Where Tags Show Up

Once applied:

* **Tag pills** appear at the top of the deck detail page.
* **Colored dots** trail the deck name in the My Decks list and in the folder tree sidebar. Hovering a dot reveals the tag name and owner (e.g. `"Aggro · Personal"` or `"Aggro · Team Alpha"`).
* **Filter chips** on My Decks list every tag you can see. Click a chip to filter the deck list to decks carrying that tag. Multiple active chips combine as "any of these" — a deck shows up if it has at least one of the selected tags.
* **Search match** — typing a tag's name into the My Decks search box surfaces decks that carry that tag, even if the deck's own name doesn't contain your query.

## Moving Decks Between Folders

When you move a deck across folders, tags follow rules consistent with their visibility:

* **Personal tags** always stay attached. You're still the deck owner; nothing about the deck's tag eligibility for personal tags changes.
* **Team tags** stay only if the deck remains in the same team. Moving a team-A deck into team-B's folder, or out of any team folder into a personal one, will strip the team-A tags — they no longer belong to a deck in that team's scope. Moving the deck back later doesn't restore them automatically; you'd reapply.


---

# 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://swu-forge.gitbook.io/docs/decks/managing-decks/tagging-decks.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.