> 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/inventory-agent-permissions/agent-installations.md).

# Agent Installations

Configure permissions for agent installation.

**Agent Installations**

Manages the deployment of XDR agents, such as downloading agent installation packages, viewing installation status and history, and tracking deployment progress.

For more information, see [Create an agent installation package](/cortex-xdr-5.x/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/create-an-agent-installation-package.md).

{% hint style="warning" %}

### Caution

Installation tokens provide access to deploy agents. Protect tokens carefully and implement token rotation policies. Consider limiting View/Edit access to dedicated deployment personnel.
{% endhint %}

| Permissions | Description                                                                                                                                | Roles Example                                                                                                                                                                                                                                                                                                          |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None        | Cannot view the **Agent Installations** page (**Inventory** → **Endpoints** → **Installations)**.                                          | <ul><li>SOC Tier-1 Analyst: Installation packages are not relevant for alert triage. Tier-1 analysts don't need to see deployment packages.</li><li>Threat Hunter: Installation packages are not relevant for hunting activities. Hunters focus on detection, not deployment.</li></ul>                                |
| View        | View the Agent Installations page for installation packages, status, and tokens.                                                           | <ul><li>SOC Tier-2 Analyst: May be useful for understanding agent deployment during investigations. Can help identify if an endpoint has an outdated installer.</li><li>SOC Tier-3 Analyst: Rarely needed for investigations, but may provide context about agent deployment history and available versions.</li></ul> |
| View/Edit   | All view capabilities, plus actions such as generating a custom package, configuring installation parameters, and managing agent versions. | Security Engineer: Essential for managing agent deployment and distribution. Must see available packages to plan deployments.                                                                                                                                                                                          |

**Required and recommended permissions**

Consider adding the following permissions:

| Permissions               | Permission Level | Reason                                                                                                                                                                                                                                                                                                                               |
| ------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Agent Administrations     | View             | Required. Installation packages deploy agents to endpoints. Without endpoint visibility, users cannot assess deployment coverage or identify unmanaged endpoints. View/Edit: Agent upgrades (Agent Management sub-option) require knowing available installation packages. Installation and endpoint management are tightly coupled. |
| Agent Prevention Policies | View             | Recommended. Understanding which policies will apply to newly deployed agents helps ensure proper protection from deployment.                                                                                                                                                                                                        |
| Agent Groups              | View             | Strongly recommended. Deployment targeting uses groups. Understanding group structure is essential for planning phased rollouts.                                                                                                                                                                                                     |
| Agent Profiles            | View             | Strongly recommended. Installation packages may include profile configurations. Understanding profiles ensures correct agent configuration during deployment.                                                                                                                                                                        |


---

# 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/inventory-agent-permissions/agent-installations.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.