> 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/reports.md).
# Reports
The "Reports Security" allows administrators to control access to individual reports within the data catalog and enable them for granular permission management.
* **Grant/Deny Access:** Define which users or roles can access specific reports.
* **Bulk Permission Management:** Efficiently update role permissions and governance roles across multiple reports simultaneously.
Based on the selected Data Source (Connection Name), the corresponding reports are displayed along with the governance roles, users, and roles with metadata and data permissions on those reports.
**Report Security and Management**
**Permissions and Governance (SGA & OE\_ADMIN only):**
* **Individual Permissions:** Add, modify, or delete metadata (view/edit) and data access (read/write) permissions for specific roles or users on individual reports.
* **Role-Based Access:** Set metadata and data permissions for roles based on the license type limitations.
**Governance Roles:**
* **Define Governance Roles:** Specify mandatory governance roles when setting up a connector (inherited by reports).
* **Update Governance Roles:** Modify governance roles for individual or multiple reports.
* **Delete Role Access:** Remove permission assignments for roles on individual or multiple reports.
**Additional Actions (SGA & OE\_ADMIN only):**
* **Define Report Admin:** Assign a role as SGA for a report, granting them the highest permissions.
* **Delete Reports:** Delete existing individual or multiple reports.
---
# 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/reports.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.
