> 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-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/configuration-permissions/auditing-permissions.md).
# Auditing permissions
Control access to Cortex AgentiX management audit logs.
Provides access to view management audit logs that track all administrative and operational activities within Cortex AgentiX. Go to **Settings → Management Audit Logs**.
The Auditing module is intentionally restricted to View-only access. Audit logs are immutable records designed to maintain compliance and forensic integrity. They cannot be modified or deleted by any user.
| **Permission** | **Description** | **Roles Example** |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None | No access to any audit logs. | SOC Tier-1 Analyst: No Need for visibility into system activities, unless context is required. |
| View | Read-only access to all audit log data.
Auditing is intentionally view-only. Audit logs are immutable records that cannot be modified or deleted to maintain compliance and forensic integrity.
| - SOC Tier-2 and 3 Analysts, and Threat Hunters: Required for case investigation and understanding event timelines.
- Security Engineer: Required for troubleshooting and validating configuration changes.
|
Required and recommended permissions
Consider adding the following permissions:
| **Permission** | **Permission Level** | **Reason** |
| -------------- | -------------------- | ------------------------------------------------------------------------- |
| Cases & Issues | View | Provides context for audit events related to cases. Strongly recommended. |
| Query Center | View | Enables XQL queries against audit datasets. Strongly recommended. |
| Dashboards | Enabled | View audit-related dashboards for operational visibility. Recommended. |
---
# 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-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/configuration-permissions/auditing-permissions.md?ask=&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.