> 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/configuration-permissions/log-collection-permissions.md).

# Log Collection permissions

Configure XDR Collectors, installers, and collection policies through **Settings** → **Configurations** → **XDR Collectors**.

| Permission | Description                                                                                                                  | Roles Example                                                                                                                                                                                          |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| None       | No access to the XDR Collectors configuration pages.                                                                         | SOC Tier-1 Analyst: Focus on issue triage; log collection configuration is not within their scope.                                                                                                     |
| View       | Read-only access to the XDR Collector menu, including configuration, administration, and groups.                             | <ul><li>SOC Tier 2 and 3 Analyst: May need to verify collection status when investigating cases.</li><li>Threat Hunter: May need to verify data collection during threat hunting activities.</li></ul> |
| View/Edit  | Full read and write access. The user can view, create, modify, and delete configurations, collection profiles, and policies. | Security Engineer: Responsible for configuring and maintaining log collection infrastructure.                                                                                                          |

### Required and recommended permissions

Consider adding the following permissions:

| Permission            | Permission Level | Reason                                                                                              |
| --------------------- | ---------------- | --------------------------------------------------------------------------------------------------- |
| Broker Service        | View/Edit        | Managing broker VMs that host collectors; collectors often run on Broker VMs. Strongly recommended. |
| Agent Profiles        | View/Edit        | Managing collection profiles referenced by policies. Strongly recommended.                          |
| Agent Administrations | View             | Viewing endpoint agents that may be related to collection. Recommended.                             |
| Data Sources          | View             | Viewing data source status related to collected logs. 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 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-xsiam/reference-and-developer-docs/role-based-access-control/configuration-permissions/log-collection-permissions.md?ask=<question>&goal=<endgoal>
```

`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.