# Tag Manager

The Tags section provides a centralized tagging system for organizing and categorizing data across your angoor.ai workspace. This feature enables administrators to create consistent labeling structures, track tag usage across different platform components, and maintain organized data classification for improved searchability and workflow management.

## Tags Dashboard

The main dashboard displays all available tags with comprehensive usage tracking and management information:

* **Label** — Tag name and identifier used across the platform
* **Usage Instances** — Number of times the tag is currently applied to users, groups, products, or other platform elements
* **Last Updated** — Timestamp showing when the tag was most recently modified or applied

<figure><img src="/files/cP62I5uX1DDStTDUt5yP" alt=""><figcaption></figcaption></figure>

## Creating Tags

Create new tags instantly through the modal interface by specifying the tag label. New tags become immediately available for assignment across all platform components including user groups, product groups, and other data entities.

<figure><img src="/files/BGyQsibCi3HmO00FRnk6" alt=""><figcaption></figcaption></figure>

## Use Cases Examples

* Categorize users, products, and groups with consistent labeling for improved data discovery and management
* Use tags as triggers for automated processes and AI agent routing based on tagged entities
* Filter and segment data by tags to generate focused reports and analyze performance across different categories
* Apply tags to control visibility and permissions for different user segments and content areas


---

# Agent Instructions: 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:

```
GET https://angoor-ai.gitbook.io/angoor-ai/basics/interactive-blocks/tag-manager.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.