> 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-xpanse/inventory/manage-business-units/modify-the-business-unit-for-an-ipv4-range.md).

# Modify the Business Unit for an IPv4 Range

You can modify the business unit (BU) assignment for an IPv4 range in the context of an incident or in the Inventory view. The following sections describe the steps.

* [How to modify the BU for an IP range in an incident](#UUID-b046f3f1-6615-9c1f-89cf-2ddc96205d8b_procedure-idm4606130427462433699216985599)
* [How to modify the BU for an IP range in the Inventory](#UUID-b046f3f1-6615-9c1f-89cf-2ddc96205d8b_procedure-idm4542112562523234120826392277)

Changes to business unit assignments may take up to an hour to appear in alerts and incidents. Review [Business Unit Management for IP Ranges](/cortex-xpanse/inventory/manage-business-units/business-unit-management-for-ip-ranges.md) to learn more about how business unit assignments work for IP ranges.

## How to modify the BU for an IP range in an incident

Business unit updates are often made in the context of an incident. Updating the business unit for one asset associated with an incident will not necessarily update the business unit for other assets associated with the same incident. You might have to update the business unit for each asset in the incident individually.

1. Navigate to **Incident Response** → **Incidents**.
2. Click on an incident in the incident list on the left.

   The incident details open in the right pane.
3. Select the **Assets** tab in the incident details.

   The assets, including IP ranges, associated with the incident are listed in the **Asset Attribution Evidence** section.

   ![incident-assets-bu.png](/files/WBZkWlCjFKMqWNLazOBh)
4. Click the edit icon ![pencil-icon.png](/files/fFjXNCVYeT9sqMjDriqC) next to **Business Units** for the IP range you want to update.

   The **Edit Asset Business Unit Tags** window will open.
5. Select one of the following options, and then click **Next**:

   * **Edit Business Units for entire IP Range**—modifies the BUs for the entire IP range.
   * **Edit Business Units for a subset IP Range**—modifies the BUs for a IP range that you define.

     Enter the **Starting IP address** and **Ending IP address** to define the custom range. You can also define the custom range in CIDR format.
   * **Edit Business Units for single IP address**—modifies the BUs for a specific IP address.

   ![edit-bu-range-incident.png](/files/Es26bnyBm2OOuJvs5nVC)
6. Add or remove business units by selecting or deselecting them in the list. Click Next.
7. Add a comment in the **Change Reason** box explaining why the change was made, then click **Next**.
8. Select how you want to handle conflicts with previously-defined ranges by choosing to **Keep previously applied business units** or **Replace all previously-applied business units**. If you choose to replace, confirm your choice by entering **REPLACE** in the dialog box.

   This step applies only if there are conflicts with previous-defined ranges with different BU assignments.

   ![resolve-conflicting-ranges.png](/files/102RUGcHhOmhFCvAGQyW)
9. Review the final list of business units to be assigned to the range. Changes to business units may impact user access to related incidents, alerts, and services, so be sure to review the specific impacts this change will have on scope-based user access. Click **Apply**.

## How to modify the BU for an IP range in the Inventory

1. Navigate to **Inventory** → **Owned IPv4 Ranges**.
2. Click on the range in the table you want to update. The details panel for that range will open.
3. Click the edit icon ![pencil-icon.png](/files/fFjXNCVYeT9sqMjDriqC) next to **Business Units** in the details panel.

   The **Edit Asset Business Unit Tags** window will open.
4. Select one of the following options, and then click **Next**:
   * **Edit Business Units for entire IP Range**—modifies the BUs for the entire IP range.
   * **Edit Business Units for a subset IP Range**—modifies the BUs for a IP range that you define.

     Enter the **Starting IP address** and **Ending IP address** to define the custom range. You can also define the custom range in CIDR format.
5. Add or remove business units by selecting them in the list. Click Next.
6. Add a comment in the **Change Reason** box explaining why the change was made, then click **Next**.
7. Select how you want to handle conflicts with previously-defined ranges by choosing to **Keep previously applied business units** or **Replace all previously-applied business units**. If you choose to replace, confirm your choice by entering **REPLACE** in the dialog box.

   This step applies only if there are conflicts with previous-defined ranges with different BU assignments.


---

# 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-xpanse/inventory/manage-business-units/modify-the-business-unit-for-an-ipv4-range.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.