> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/account-and-team/tags/how-to-use-tags.md).

# How to use tags

Tags are one shared, account-wide vocabulary you can apply to journey maps, cards, personas, portfolio items, and metrics, then use to filter each of those areas down to what you want to see.

{% hint style="info" icon="clipboard-list" %}

#### In this guide

1. [Data-level and card-level tags](#data-level-and-card-level-tags)
2. [Apply a tag](#apply-a-tag)
3. [Filter by tags](#filter-by-tags)
   {% endhint %}

Tags belong to categories, and each category carries an icon and color that every tag inside it inherits. You build that vocabulary once in **Account Settings**. To create categories and the tags inside them, see [How to create and edit tags](/account-and-team/tags/how-to-create-and-edit-tags.md). This article assumes the tags you need already exist and covers applying and filtering by them.

#### Data-level and card-level tags

Most items carry tags at one level. A card on a journey map can carry tags at two, and the difference decides how far a tag reaches.

{% columns %}
{% column %}
**Data-level tags**

Applied to the underlying item: a journey map, persona, portfolio item, or metric. The tag travels with that item everywhere it's used, across every map in the account.
{% endcolumn %}

{% column %}
**Card-level tags**

Applied to one card on one journey map. The tag stays on that single instance. If the same portfolio item sits on three maps, a card-level tag on one map does not carry to the other two.
{% endcolumn %}
{% endcolumns %}

***

#### Apply a tag

Where you add a tag depends on whether you want it to follow the item everywhere or stay on a single card.

To tag a journey map, open its tag field in either place: the **Journey information** modal inside the map editor, or **Manage tags** in the three-dot menu on the map's row in the journey map list. Both open the same picker, where you choose tags grouped by their category.

<figure><img src="/files/Z5b1IiioPdrEroh1GAxh" alt="The Journey information modal in the journey map editor. It shows Name, Description, Performance Indicator, Coordinator, and a Tags field holding several applied tag chips, each with its category color and icon, above Cancel and Save buttons."><figcaption><p>Tagging a journey map from the Journey information modal</p></figcaption></figure>

<figure><img src="/files/AzKRKOEMStFly2CXBiVN" alt="The journey map list with a row&#x27;s three-dot menu open and Manage tags highlighted. An Edit journey map tags modal is open beside it, showing applied tag chips and a dropdown of tags grouped by category to add or remove."><figcaption><p>Tagging a journey map from its row in the list</p></figcaption></figure>

Personas, portfolio items, and metrics each carry their own data-level tags. On a persona, use the **Tags** field in the info panel of the persona editor. On a portfolio item or a metric, use the **Tags** field with its **+ Add** control in the item's details. The tag applies to that item wherever it appears.

To tag a single card, select it to open the card details panel and use the **Tags** section. Card tags sit alongside the card's **Personas** and **Comments** and stay with this one card on this one map.

<figure><img src="/files/FmHdKv0622vA8c433DU5" alt="A journey map card selected with its details panel open. The Tags section shows two tag chips, each with its category color and icon, between the Personas and Comments sections. The card itself shows a small tag-count badge."><figcaption><p>Card tags in the card details panel</p></figcaption></figure>

For the full card details panel, including personas and comments, see [How to add and edit cards](/journey-maps/cards/how-to-add-and-edit-cards.md).

***

#### Filter by tags

Tags filter content within each area. The shared vocabulary lets you reuse the same tag in several places, but each list and each map filters only its own items.

{% hint style="warning" %}

#### **Important: Tags do not filter across areas**

A tagged persona that appears on a map does not surface that map when you filter the journey map list by the persona's tag. Filtering the map list shows maps; filtering personas shows personas. To narrow a map's own content, filter the map by card tags instead.
{% endhint %}

The journey map, persona, portfolio, and metric lists each filter by tag. Open **Filters**, choose **Tags**, and pick one or more. Tags appear with their category color so you can tell similar tags apart, and a `[no tag set]` option finds untagged items. The result narrows in place, and you can save a filter as a named view for reuse.

<figure><img src="/files/MQlxwcOHvv9VEmw5ZZ7n" alt="The journey map list filtered by tag. Saved-view tabs run across the top (All maps, plus named views). The Filters panel is open with a Tags submenu showing tags grouped by category with checkboxes, and an active filter chip with a Clear control above the list."><figcaption><p>Filtering the journey map list by tag, with saved views across the top</p></figcaption></figure>

Saved views turn tags into something close to folders. Tag your maps by theme, project, or stage, then save each tag filter as a view to switch between groupings without re-filtering each time.

<figure><img src="/files/eutahYzUE2erM8OvK2DV" alt="The Personas list filtered by a tag. Saved-view tabs run across the top (All personas, Research based, Assumption based), with an active Tags filter chip and a Clear control above the persona rows."><figcaption><p>Saved views on the persona list, each backed by a tag filter</p></figcaption></figure>

Inside the map editor, open **Filters** to filter the map's content by **Tags** alongside **Lanes** and **Personas**. By default this searches both data-level and card-level tags; an option narrows it to card-level tags only. As on lists, tags show with their category color and a `[no tag set]` option finds untagged cards.

<figure><img src="/files/xLRlrdvN8h9SYsCiAbb8" alt="The Filters panel open in the journey map editor. It lists lane checkboxes, a Personas section, and a Tags section showing tags with their category color prefix and checkboxes, plus a Save this filter as a View input at the bottom."><figcaption><p>Filtering a map by Lanes, Personas, and Tags in the editor</p></figcaption></figure>

For multi-tag matching, clearing filters, and saving the filter as a view, see [How to filter a journey map](/journey-maps/filtering-and-views/how-to-filter-a-journey-map.md).

#### Related topics

<table data-column-title-hidden data-view="cards"><thead><tr><th>Article</th><th>What it covers</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>How to create and edit tags</strong></td><td>Build your tag categories and the tags inside them in Account Settings.</td><td><a href="/pages/PCBq72fBl1XKlVm9m8al">/pages/PCBq72fBl1XKlVm9m8al</a></td></tr><tr><td><strong>How to filter a journey map</strong></td><td>The full filter panel: lanes, personas, tags, multi-tag matching, and clearing.</td><td><a href="/pages/TvWyNP7bpL7PzUBbgLJ2">/pages/TvWyNP7bpL7PzUBbgLJ2</a></td></tr><tr><td><strong>How to manage personas</strong></td><td>The persona list, its columns, and filtering personas into saved views.</td><td><a href="/pages/oScEAxHrtqqY2twvz5kM">/pages/oScEAxHrtqqY2twvz5kM</a></td></tr></tbody></table>


---

# 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://helpdesk.smaply.app/account-and-team/tags/how-to-use-tags.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.