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

# Asset Notes

In Expander, you can add notes to individual assets as a way to provide additional context about the asset. Notes can be added to all asset types except services and websites, and are limited to 1024 characters. Notes are displayed as a field in the **Inventory**, so you can filter and sort on them. Notes are also displayed on the **Assets** tab of incidents. You can add or edit Notes on the asset details pane or on the Assets tab of an incident.

## Add a Note to an Asset in an Incident

When you add a note to an asset in an incident, the note will apply to that specific asset. The note will not automatically be applied to other assets associated with the same incident.

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.
4. Type your note in the **Notes** text box for the appropriate asset. Click outside the text box to save the note.

   ![asset-notes-incident.png](/files/I4xVFHsxa3zdstlifEbv)

## Add a Note to an Asset in the Inventory

1. Navigate to **Inventory**, and select **All Assets** or a specific asset page.
2. Click on an asset in the list to open the asset details panel.
3. Type your note in the **Notes** text box in the asset details panel. Click outside the text box to save the note.

## Update an Existing Asset Note

Click the edit icon ![pencil-icon.png](/files/fFjXNCVYeT9sqMjDriqC) next to **Notes** to edit an existing note.


---

# 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/asset-notes.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.