> For the complete documentation index, see [llms.txt](https://docs.graphite-note.com/graphite-note-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphite-note.com/graphite-note-documentation/account-and-team-setup/tags.md).
# Tags
The Tags Page in Graphite Note is used to manage tags that help in organizing and distinguishing datasets, models, and notebooks. Tags improve searchability and allow users to categorize resources effectively. Note that only one tag can be assigned to each dataset, model, or notebook. The Tags Page can be accessed by clicking the wheel icon (⚙️) in the top-right corner and selecting Tags.
### Tag List
Displays all created tags with their name, description, color, and a preview of how the tag appears.
***
### Creating new Tag
To create a new tag, users can define its name and description while selecting a color for visual distinction. This allows tags to be uniquely identifiable and easy to manage. Tags can also be edited or deleted using the action icons, providing flexibility for keeping the tagging system up-to-date.
### Tag creation in Datasets, Models and Noteboks
Additionally, tags can also be created during the process of creating a new dataset, model, or notebook, or within the settings options of an existing dataset, model, or notebook. This ensures that tagging remains a flexible and integrated part of resource management.
---
# 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.graphite-note.com/graphite-note-documentation/account-and-team-setup/tags.md?ask=&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.
