> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/basic-concepts/tagging.md).

# Tagging

Tags are used for filtering and organizational purposes

**For example**: tagging a Aubrey Chair with the following tags #product, #chair, #Fall2022, #AubreyCollection

There are three types of tags:

1. **Item/Asset Tags** 
   1. Can only be added to Items, Stages, and Assets
   2. They have their own Tag Management section available under the Items section
2. [**Node Tags**](/platform-documentation/catalog-2.0-docs/project-data/assets/nodes/common-properties/node-tags.md)
   1. They can only be added to Nodes inside Assets
   2. Used in Asset Logic, certain Operators, and Composite Assets
3. **Attribute Tags**
   1. They can only be added to Global Attributes
   2. Typically used only in Front-End Logic, to filter attributes

Item Tags, Node tags or Attribute Tags  with the same name can co-exist, and would not interfere with each other, as their use is completely separate from each other


---

# 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://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/basic-concepts/tagging.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.