> 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.md).

# Security

Data Object Security features and functionalities are described, with a focus on access control managed through roles and permissions. Administrators define who can view or edit data at various levels.

**Key areas of security:**

* **User Access and Roles:** Administrators can assign different permission levels to users based on their roles. These permissions control what data users can view or edit (reports, dashboards, etc.).
* **Data Security:** Administrators can grant or deny access to specific data sources (databases, tables, reports, dashboards, APIs, etc.) for individual users or roles. Permissions can be set for individual objects or inherited from higher levels. Advanced features like column-level security and data masking offer even finer control.
* **Governance Roles:** Predefined roles (Owner, Steward, Custodian) ensure proper data management. Administrators can also define custom roles, which can be assigned to data sources during setup or later.
* **Application Security:** Granular access controls within the OvalEdge application itself. Administrators can restrict access to specific functionalities based on user roles and licenses.

**Object Security**

* **Role-Based Access Control (RBAC)**\
  Organizations often define Roles with specific responsibilities to simplify access management. OvalEdge Administrators create Roles and assign permissions to control access to various data objects.
* **User-Based Access Control (UBAC)**\
  OvalEdge Administrators create Users and assign permissions to control access to various data objects.
* **Governance Roles**\
  Many organizations have specialists like Stewards (subject matter experts), Custodians (data curation specialists), and Owners (data asset authorities) to maintain data quality. OvalEdge supports assigning these Governance Roles to manage and maintain data integrity.&#x20;

{% hint style="info" %}
Please refer to the Users & Roles article to learn about license types, meta permissions, data permissions, and how to create users and roles.
{% endhint %}

## Security

Users with an author license can access the security module. However, only specific administrator roles have the privilege to view and define the security of various data objects.

**Administrator Roles and Responsibilities**

For details on OvalEdge Administrators' roles and responsibilities, refer to the "Users & Roles" article's section on "Different Administrators of OvalEdge & their Responsibilities."

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf5dSQN655oDPU_XoaJHUsNkqMnBtKsVv-fIqUs4LhLtPPTGflxYg4mK-1XUAwfQYfw-hBTweu57_MeHJjtIJW6Bhl1R4B0J6zndkyCVBUUZDGPtIxs7nZQGJHYdXTDyvv1MhwhZA?key=HQ3_DdDr7Hskac9eJBoI-Xdv" alt=""><figcaption></figcaption></figure>


---

# 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.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.
