> 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.3/tags/master-tags.md).
# Master Tags
Master Tags serve as the top-level classification in the tagging hierarchy, acting as domains or containers for regular tags. They provide a structured way to organize and govern tags within the system. Depending on the security model, Master Tags can function in two ways: in an Open mode, where all users can freely view and use tags for broad collaboration and discovery; or in a Secure mode, where governance roles such as Owner, Steward, and Custodian control access, management, and additional features like custom fields and widget visibility. For example, a Master Tag such as Finance may contain regular tags like Invoices, Budgets, and Tax Records, with its governance either fully open or role-based, ensuring flexibility in organizational control and transparency.
***
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release8.3/tags/master-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.