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

# Tags

Add tags to your Guideflow's to categorize them and make them easier to find across your workspace.

{% hint style="info" %}
Tag your Guideflow's by product feature, sales stage, or customer type so your team can quickly filter and find the right demo at the right time.
{% endhint %}

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/yr47xgyulr>" %}

### **How to add tags to a Guideflow**

* Open your Guideflow in the editor.
* Click **Settings** in the right panel.
* Under **Tags**, type a tag name and select it to apply it to the Guideflow.
* Add as many tags as needed.

{% hint style="info" %}
Tags are applied at the individual Guideflow level. You can add multiple tags to a single Guideflow.
{% endhint %}

***

### How to filter by tags in the dashboard?

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/8ko5w25a5p>" %}

* Navigate to your Guideflow dashboard.
* Use the **Tags** filter to search and filter Guideflow's by any tag you have created.

***

### Tag ideas to get you started

You can develop your own tagging strategy based on how your team works. Here are a few examples:<br>

* **Product feature:** "Payments", "Analytics", "Onboarding"
* **Customer type:** "Enterprise", "SMB", "Self-serve"
* **Sales stage:** "Prospecting", "Qualification", "Proposal"
* **Team:** "Sales", "Marketing", "Customer Success"

> Tags can also be managed from your workspace settings under **Settings** → **Tags**.


---

# 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.guideflow.com/help/edit-your-guideflow/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.