> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-add-arrows-to-my-connections.md).

# How do I add arrows to my connections?

{% hint style="info" %}
Arrows can't be added to connections if you're using the [SNA template](/guides/templates.md#sna-social-network-analysis-template).
{% endhint %}

If you want to add arrows to your connections to specify direction, here are a couple ways to do so:

### For a single connection

* Select the connection.
* Use the direction icon ![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-b33aa97e67d12cb18b1af944d1d0c893796de62b%2Fexchange-alt.svg?alt=media) in the [side panel](/overview/user-interfaces/map-editor.md#side-panel) to specify "Directed", "Mutual", or reverse the connection direction.
* Click "Directed" to add a connection arrow, and "Mutual" to add an arrow on each side.

### For all connections

* Press `Shift` + `C` on your keyboard to select all connections.
* Click on the direction icon ![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-b33aa97e67d12cb18b1af944d1d0c893796de62b%2Fexchange-alt.svg?alt=media) in the side panel.
* Click "Directed" to add arrows to all connections.

### For a specific group of connections

* Click the Search bar at the top of the map, then click the rocket icon ![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-789eead0a25caae6c17d918b2940828c7bad678b%2Frocket.svg?alt=media) on the far right to bring up the selector builder.
* Use the selector builder to select the connections that you want to change, based on the information in their profiles.
* Click on the direction icon ![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-b33aa97e67d12cb18b1af944d1d0c893796de62b%2Fexchange-alt.svg?alt=media) in the side panel.
* Click "Directed" to add arrows to your selected connections.

### For imported connections and connections created by clustering

If your connections are imported from Excel, imported from a remote source ([Google Sheets](/guides/import.md#import-from-google-sheets) or a [JSON blueprint](/guides/import/blueprints.md#set-a-remote-blueprint)), or created by [clustering](/guides/clustering.md), you can add arrows by changing the default map settings:

* [Open the map settings](/overview/user-interfaces/settings.md#map-settings)
* Click **Default connection direction**
* Choose **Directed** to add arrows to one end, and choose **Mutual** to add arrows to both ends

You can also add arrows to imported connections if you include a `direction` field in your import file (for example, by adding a new spreadsheet column titled `direction`). In that field, you can use one of the following values (must be entered in all lowercase letters):

* `directed`
* `undirected`
* `mutual`

{% hint style="info" %}
When you're imported from a connected Google Sheet or JSON blueprint, you can only choose **one** connection direction. All of the connections in your map will have that same direction.
{% endhint %}

{% hint style="info" %}
Kumu recognizes connection direction from your spreadsheet import (**From** and **To** columns in your connections sheet) or the direction you draw the connection by hand. This connection direction determines which way arrows point when you specify a "directed" connection.
{% endhint %}


---

# 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://docs.kumu.io/frequently-asked-questions/how-do-i-add-arrows-to-my-connections.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.