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

# About Tags

Tags allow users to group data objects and other assets logically. Grouping similar data facilitates efficient data management and makes it easier to locate related data objects. For example, if a user manages a large dataset for the Finance Department, they can assign a "Finance" tag to relevant tables, files, and reports. It makes it easy for them to identify and view all data related to their department. Once data objects are tagged, users can filter by tags and perform various actions on the data.

Supported Objects:\
Tags can be assigned to the following data object types:

* Schemas
* Tables
* Table Columns
* Files
* File Columns
* Reports
* Report Columns
* Codes
* APIs
* API Attributes
* Business Terms
* Data Stories
* Data Quality Rules

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# 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.ovaledge.com/release8.2/tags/about-tags.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.
