> 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/administration/security/governance-roles.md).
# Governance Roles
OvalEdge offers a foundation for data governance with three predefined roles:
* **Owner:** Ultimately responsible for a data object's accuracy, quality, and policy adherence. A user assigned as Owner for an Object would be getting Meta Write on it, although the user may not have Meta read explicitly.
* **Steward:** Oversees the data object's usage and ensures alignment with business needs. A user assigned as Steward for an Object would be getting Meta Write on it, although the user may not have Meta read explicitly.
* **Custodian:** Manages the technical aspects of the data object, including security and access control. A user assigned as Custodian for an Object would be getting Meta Write on it, although the user may not have Meta read explicitly.
**Customization (Admin Users Only)**
Administrators can extend this framework by defining additional data governance roles (Gov 4, Gov 5, Gov 6) with customized descriptions to match the organization's specific needs and compliance requirements.
---
# 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/administration/security/governance-roles.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.