> 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/governance-catalog/governed-data-query/roles-and-permissions.md). # Roles and Permissions By default, Governed Data Queries (GDQs) can be created by roles with Domain Meta Read permissions and OE\_Admin access. Additionally, Admins have the privilege to configure specific roles to grant execution privileges to roles who would be called GDQ Admins and need basic Domain Read permissions to create GDQ. Navigate to **Administration > System Settings > Users & Roles > Key** (ovaledge.GDQ.admin).
| Action | GDQ Admin (With Domain Access - Meta Read) | OvalEdge\_GDQ Admin / OE\_Admin (No Domain Access) | Steward of GDQ | Viewer | Author Role (If not restricted to Application Security) | | ----------------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------- | ------------------------------------------------------- | | Create GDQ | ✅ Allowed | ❌ Not Allowed |

❌ Not Allowed


✅ Allowed if GDQ Admin

| ❌ Not Allowed | ❌ Not Allowed | | View GDQ | ✅ Allowed (if Meta Read is granted on the domain) | ✅ Allowed (if Meta Read is granted on the domain) \| GDQ is not shown if access is not present | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | | Edit GDQ | ✅ Allowed | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ❌ Not Allowed | | Configure Terms | ✅ Allowed | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ❌ Not Allowed | | Add New Entries | ✅ Allowed | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ❌ Not Allowed | | Execute GDQ | ✅ Allowed | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ❌ Not Allowed | | Delete GDQ | ✅ Allowed | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ❌ Not Allowed | | Delete Entries | ✅ Allowed | ❌ Not Allowed | ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ❌ Not Allowed | | View Results (Entries Found - Data) | ✅ Allowed (if Meta Read is granted on the domain) |

✅ Allowed (if Meta Read is granted on the domain)

❌ Not Allowed is Access on Domain is not Present

| ✅ Allowed (if Meta Read is granted on the domain) | ❌ Not Allowed | ✅ Allowed (Only for GDQs they have access to) | | View Data in Entries (Results Page) | ✅ Allowed (Only for data they have access to) | ✅ Allowed (If Meta Read is granted on domain & Only for data they have access to) | ✅ Allowed (Only for data they have access to) | ❌ Not Allowed | ✅ Allowed (Only for data they have access to) | *** 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/governance-catalog/governed-data-query/roles-and-permissions.md?ask=&goal= ``` `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.