> 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/dashboards-and-reports-permissions/reports-permissions.md).
# Reports permissions
Controls access to the generation and management of documented security summaries, ranging from shift handoffs to compliance evidence
Cortex XDR enforces least-privilege per-object access by allowing you to manage access for custom (user-defined) report templates. For more information, see [Manage access to objects](/cortex-xdr-5.x/onboard-cortex-xdr/post-deployment-steps/manage-user-roles-and-access-management/manage-access-to-objects.md).
| Permission | Description | Roles Example |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Enabled | Access permissions change depending on the per-object access and sub-permissions granted as explained below. For example, when Reports are enabled users can view existing reports, but access to the Widget Library is dependent on Editor permissions.
Other access permissions include create, manage, and delete report templates, and generate new reports.
When set to Enabled, you can grant the following additional permissions:
- Create Report Templates: Enables the New Template button, allowing the user to create new custom report templates. The user who creates the report template is designated as the Owner.
- Edit Public Report Templates: Allows the user to modify custom report templates set to Public, even if they are not the Owner.
| Most roles should be able to view and edit reports. |
| Disabled | Users cannot access reports or report templates. | |
### Required and recommended permissions
Reports rely on populating data from various functional modules. For reports to be complete, consider the following dependencies:
| Permission | Permission Level | Reason |
| --------------------- | ---------------- | --------------------------------------------------------------------------------------------- |
| Cases & Issues | View | Required. Reports containing cases/issue statistics require this permission to populate data. |
| Agent Administrations | View | Strongly Recommended. Reports containing endpoint metrics require this permission. |
| Asset Inventory | View | Recommended: Reports containing asset information require this permission. |
| Compliance | View | Recommended. Compliance reports require this permission to include compliance metrics. |
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/reference-and-developer-docs/role-based-access-control/dashboards-and-reports-permissions/reports-permissions.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.