> For the complete documentation index, see [llms.txt](https://learn.squirrel365.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.squirrel365.io/components-functions-and-connections/overview/charts/chord-diagram.md).

# Chord Diagram

{% hint style="success" %}
**Who can use this feature?**

All Squirrel365 plans include the Chord Diagram component. 

For more details, see our [**pricing comparison matrix**](https://squirrel365.io/pricing/).
{% endhint %}

he **Chord Diagram** is a data visualization component that displays weighted relationships between several entities and data points.

<figure><img src="/files/Zk00SbOltuCx6H1h5Tnk" alt="" width="428"><figcaption></figcaption></figure>

## Chord Diagram Properties

The **Chord Diagram** component properties consist of **LAYOUT & POSITIONING, DATA**, and **DYNAMIC VISIBILITY** drawers.

This guide will describe all sections besides the [**Layout & Positioning**](/components-functions-and-connections/overview/layout-and-positioning.md) and [**Dynamic Visiblity**](/getting-started/core-concepts/dynamic-visibility.md) sections, as these are generic to each component. A separate guide and tutorial for each can be found by clicking the links above.

The component properties are set and edited using different methods, some have multiple methods, some just one. See this [Set Property Values](https://squirrel365.io/knowledgebase/set-property-values/) article for more information on using the different methods.

***

### DATA

* **From** - an input field that needs to be bound to the spreadsheet. Contains the start points for the ribbons.
* **To** - an input field that needs to be bound to the spreadsheet. Contains the endpoints for the ribbons.
* **Value** - an input field that needs to be bound to the spreadsheet. Contains the values tied to the ribbons.

{% hint style="info" %}
Both ranges must match in size. In the screenshot below, the ribbons connect as the following:

* A to D = 10
* B to D = 8
* B - E = 4
* and so on...
  {% endhint %}

<figure><img src="/files/ppgJBjarZDmi5ZOUETU7" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/IQBLGQO8kE3sTlAtmBSs" alt=""><figcaption></figcaption></figure>

#### STYLING

* **Allow Hover to change ribbon opacity** - an option to allow an opacity property to be applied to the Chord ribbons when hovered over.
  * **Hover Opacity** - an input that determines the Hover Opacity.
* **Ribbon Opacity** - an input that determines the default Ribbon Opacity.

<figure><img src="/files/VdJePR86ZRzevunxmDmE" alt=""><figcaption></figcaption></figure>


---

# 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://learn.squirrel365.io/components-functions-and-connections/overview/charts/chord-diagram.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.