> 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-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-management/indicator-relationships/leverage-relationships-in-the-canvas.md).

# Leverage Relationships in the Canvas

Use Canvas indicator relationships to enrich investigations in Cortex XSOAR 6.15.

Within an incident, you can use the Canvas to further explore and see if any of the indicator relationships provide more information.

1. Within an incident, navigate to the **Canvas** tab.
2. On the Canvas, click your incident.

   The Quick View window is displayed.
3. Navigate to the **Indicators** tab.

   The indicators for this incident are displayed with their current verdict. For example, benign indicators have a green background, malicious indicators have a red background, and unknown indicators have a grey background.
4. Drag the indicators you want to further investigate on to the canvas.
5. Hover over an indicator on the canvas and click the blue arrow icon.

   A menu with several options appears.
6. To view the indicator’s relationships, click **Expand**.

   If the indicator has additional relationships, those relationships are added to the canvas.
7. Click the indicator to view additional information about it and any possible relationships that might exist.


---

# 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-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-management/indicator-relationships/leverage-relationships-in-the-canvas.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.