> 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.2/administration/security/dashboards.md).
# Dashboards
The "Dashboard Security" allows administrators to control access to system and custom dashboards, ensuring data security and user visibility.
**Dashboard Types:**
* **System Dashboards:** Pre-built dashboards offer immediate insights into key metrics, eliminating configuration needs.
* **Custom Dashboards:** Allow users to create personalized dashboards with their preferred reports and organization.
* **Favorites Dashboards:** Individual user workspaces for managing and organizing reports based on their needs. (Automatically created for each user.)
**Security Features (Administrators only):**
* **Control Access:** Define who can view, manage, and add reports to different dashboard types.
**Dashboard Permissions**
OE\_ADMIN and users with the "ovaledge.role.admin" role can manage access permissions for dashboards (system, custom, and favorites).
* **Grant/Deny Access:** Control which users or roles can view, manage, and add reports to different dashboards.
* **Bulk Permission Management:** Efficiently update role permissions across multiple dashboards simultaneously.
**Detailed Permission Management:**
* **Individual Permissions:** Add, modify, or delete metadata (view/edit) permissions for specific roles or users on individual dashboards.
* **Role-Based Access:** Set metadata permissions for roles based on license type limitations.
**Additional Actions:**
* **Define Dashboard Admin:** Assign a role as admin for a dashboard, granting them the highest permissions (OE\_ADMIN or "ovaledge.role.admin" only).
* **Delete Dashboards:** Delete existing dashboards.
---
# 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/release8.2/administration/security/dashboards.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.