> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/scenarios/management/tags.md).
# Tags
Tags help you organize and filter scenarios by department, quarter, project, or status.
### Adding Tags to Scenarios
1. Click **⋮** on any scenario
2. Select **Change Tag**
3. Choose an existing tag from the dropdown or type a new tag name
4. Press **Enter**
The tag appears as a label on the scenario card.
### Common Tag Examples
**By Department** — Engineering, Sales, Marketing, Product, Operations, Finance
**By Planning Cycle** — Q1 2026, Q2 2026, H1 2026, FY27
**By Purpose** — Budget Cuts, Growth Plans, Reorgs, Hiring, Succession
**By Status** — Draft, In Review, Approved, Implemented
**By Project** — AI Initiative, Expansion EMEA, GTM Realignment
**Tip:** Use consistent naming conventions across your organization (e.g., always "Q1 2026" not "q1-2026").
## Multiple Tags
Some organizations support multiple tags per scenario (e.g., "Engineering" + "Q2 2026" + "Hiring"). Check with your admin to see if this is enabled. If only single tags are supported, use compound tags like "Engineering - Q2 2026".Tags
Tags help you organize and filter scenarios by department, quarter, project, or status.
## Best Practices
* **Be consistent** — Agree on tag naming conventions with your team
* **Clean up regularly** — Archive or delete tags for old quarters and completed projects
* **Combine with scenario names** — Tags complement clear scenario naming, they don't replace it
---
# 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://docs.agentnoon.com/scenarios/management/tags.md?ask=&goal=
```
`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.