> 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-assets-permissions/network-configuration-permissions.md).

# Network Configuration permissions

Network Configuration (**Inventory** → **Assets** → **Network Configuration**) enables administrators to define and manage the organization's network topology, such as internal and external IP address ranges, internal domain suffixes, and trusted networks.

{% hint style="info" %}

### Notice

External IP address ranges: Requires an ASM license.

Trusted Networks: Requires a Cloud Posture Security or Cloud Runtime Security license.
{% endhint %}

Network topology configuration is frequently shared between the Security and IT Infrastructure teams. Ensure proper coordination before altering IP ranges or trusted network definitions.

For more information, see [Network configurations](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/asset-management/asset-configurations/network-configuration.md).

The Network Configuration permission controls the ability to view, create, and edit network topologies, IP ranges, and trusted domains.

| Permissions | Description                                                                                                   | Roles Example                                                                               |
| ----------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| None        | No access to the Network Configuration menu, IP ranges, internal domains, or trusted networks.                | SOC Tier-1 Analyst: Does not need access to network configuration.                          |
| View        | Read-only access to view defined IP ranges, internal domains, and trusted networks.                           | SOC Tier-2 and 3 Analysts, and Threat Hunters: Do not need access to network configuration. |
| View/Edit   | Full access to add, edit, and delete IP address ranges, internal domains, and trusted network configurations. | Security Engineer: Responsible for maintaining network configuration.                       |

**Required and recommended permissions**

Consider adding the following permissions:

| Category              | Permissions | Reason                                                                                         |
| --------------------- | ----------- | ---------------------------------------------------------------------------------------------- |
| Asset Inventory       | View        | Strongly recommended to view assets associated with IP ranges. View/Edit for Asset Management. |
| Agent Administrations | View        | Recommended for endpoint details linked to network ranges.                                     |
| Query Center          | View        | Recommended to run XQL queries on network data.                                                |


---

# 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/inventory-assets-permissions/network-configuration-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.