> 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/administration/security/master-tags.md).

# Master Tags

The “Master Tags Security” allows administrators to control user access and the widget's presence on the Home Page.

* **Grant Permissions:** Administrators can define who can use master tags, allowing or denying access for specific user roles or individuals.
* **Set User Permissions:** Grant granular access to various functionalities. For example, editors can add tags but not delete them. Permissions can also be modified or revoked.
* **Configure Widget Visibility:** Administrators can choose whether the master tags widget appears on the homepage or during onboarding, making it easy for users to discover the system.&#x20;

  <figure><img src="https://content.gitbook.com/content/8fgltewNgYZ8ucAp7Svt/blobs/L91xrJ8m75jUhJzVL2Fv/image.png" alt=""><figcaption></figcaption></figure>

  **Master Tags Permissions (SGA & OE\_ADMIN only)**

  Users with SGA and OE\_ADMIN roles can manage access permissions for master tags within OvalEdge.

  * **Grant/Deny Access:** Control which users or roles can view or edit master tags.
  * **Bulk Permission Management:** Efficiently update role permissions across multiple master tags simultaneously.

  **Detailed Permission Management:**

  * **Individual Permissions:** On each master tag, add, modify, or delete metadata (view/edit) permissions for specific roles or users.
  * **Role-Based Access:** Set metadata permissions for roles based on license type limitations.

  **Governance Roles**

  * **Update Governance Roles (Individual/Bulk):** Modify governance roles for a single or multiple master tags.
  * **Delete Role Access:** Remove permission assignments for roles on individual or multiple master tags.

  **Additional Actions:**

  * **Define Master Tags Admin:** Assign a role as admin for a master tags, granting them the highest permissions (OE\_ADMIN only).
  * **Configure Widgets:** It allows admin users to select master tags and root tags to display in the Find Datasets Anywhere widget on the Home Page. The admin can choose a master tag and its corresponding root tags and enable the toggle to display these tags in the widget.
  * **Create Master Tags:** It allows users to create a new master tag and configure Governance roles such as Steward, Custodian, and Owner.
  * **Edit Master Tags:** It allows users with Metawrite permissions to modify the selected master tag name.
  * **Delete Master Tags:** It allows users with Metawrite permissions to modify the selected master tag name.


---

# 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/administration/security/master-tags.md?ask=<question>&goal=<user_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.
