> 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-asset.md).

# Modify the Business Unit for an Asset

Update the business unit assignment for an asset in the context of an incident or in the Inventory.

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

* [How to modify the BU for an asset in an incident](#UUID-d8ee547c-b37e-1fdb-c2dd-052c4f40a7cf_procedure-idm4606130427462433699216985599)
* [How to modify the BU for an asset in the Inventory](#UUID-d8ee547c-b37e-1fdb-c2dd-052c4f40a7cf_procedure-idm4611658766748834120965143129)

The steps are slightly different for IPv4 ranges, so refer to [Modify the Business Unit for an IPv4 Range](/cortex-xpanse/inventory/manage-business-units/modify-the-business-unit-for-an-ipv4-range.md) for those details.

Changes to business unit assignments may take up to an hour to appear in alerts and incidents. Review [Manage Business Units](/cortex-xpanse/inventory/manage-business-units.md) to learn more about how business unit assignments work.

## How to modify the BU for an asset 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.

   Each asset associated with the incident is listed in the **Asset Attribution Evidence** section.

   ![incident-assets-bu.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-e3e0e0eb627c770042bf2cc02a72b60c42fd630b%2F24fbb98d447ba6084d7785d7a773f793749154f0f8f02911fe768d7eb4ec61d8.png?alt=media)
4. Click the pencil icon ![pencil-icon.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-b31f7312a9b18ffcd3ab62f68c516f342a53cd43%2F69c07cd9f57a109d8ad339e842b25477a390426c49ac67e88387a181a39775c8.png?alt=media) next to **Business Units** for the asset you want to update.

   The **Edit Asset Business Unit Tags** window will open.
5. Add or remove business units by selecting them in the list. If the asset is a parent domain, select **Make changes to related subdomains** if needed. Click **Next**.

   ![add-bu-screen.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-4ca43d5e390c7ad04fbb79ca63c9f98b0749c862%2F017eb66dafa6246bac738281a751bfc21fb390907e3dd0aaec55339d280ae41f.png?alt=media)
6. Add a comment in the **Change Reason** box explaining why the change was made, then click **Next**.
7. Review the final list of business units to be assigned to the asset. Also review the specific impacts this change will have on scope-based user access. Click **Apply**.

   Note that the change may impact user access to incidents, alerts, and services in addition to the asset.

## How to modify the BU for an asset in the Inventory

1. Navigate to **Inventory** and open the **Unified Inventory** or one of the asset type pages from the main menu.
2. Click on the asset in the table you want to update. The details panel for that asset will open.
3. Click the edit icon ![pencil-icon.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-b31f7312a9b18ffcd3ab62f68c516f342a53cd43%2F69c07cd9f57a109d8ad339e842b25477a390426c49ac67e88387a181a39775c8.png?alt=media) next to **Business Units** in the details panel.

   The **Edit Asset Business Unit Tags** window will open.
4. Add or remove business units by selecting them in the list. If the asset is a parent domain, select **Make changes to related subdomains** if needed. Click **Next**.
5. Add a comment in the **Change Reason** box explaining why the change was made, then click **Next**.
6. Review the final list of business units to be assigned to the asset. Also review the specific impacts this change will have on scope-based user access. Click **Apply**.

   Note that the change may impact user access to incidents, alerts, and services in addition to the asset.


---

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