> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/reference-and-developer-docs/role-based-access-control/dashboards-and-reports-permissions/ingestion-monitoring-dashboard-permissions.md).

# Ingestion Monitoring dashboard permissions

Manage access to Cortex XSIAM data ingestion monitoring dashboards.

Access to the Data Ingestion Dashboard, which provides an overview of data ingestion by product and vendor:

* Daily quota consumption: Tracking used data limits against the organization's allowance.
* Data ingestion rates: Visualizing the velocity of incoming data.
* Source Health: Ensuring that various data sources and products are communicating correctly with Cortex XSIAM.

| Permission | Description                                       | Roles Example                           |
| ---------- | ------------------------------------------------- | --------------------------------------- |
| None       | No access to the Data Ingestion Dashboard.        |                                         |
| View       | Read-only access to the Data Ingestion Dashboard. | Most roles should have view permission. |

### Required and recommended permissions

To effectively utilize the ingestion monitoring tools, consider these dependencies:

| Permission   | Permission Level | Reason                                                                 |
| ------------ | ---------------- | ---------------------------------------------------------------------- |
| Dashboards   | Enabled          | Required to access the dashboard.                                      |
| Query Center | View             | Recommended for deeper analysis of ingestion data through XQL queries. |


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam/reference-and-developer-docs/role-based-access-control/dashboards-and-reports-permissions/ingestion-monitoring-dashboard-permissions.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.