> 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-size-elements-by-number-of-connections.md).

# How do I size elements based on number of connections?

Want to know which element is the most well-connected? Here's where combining metrics and sizing comes in handy.

## Run metrics

First, you'll have to run metrics to let Kumu calculate the number of connections of each element for you:

1. Click on the "Metrics" icon in the bottom right corner of the map
2. Select "Social Network Analysis" to open up the Metrics menu
3. Choose the "degree" metric from the dropdown list
4. Click the large button "Discover the connectors/hubs" to see the results
5. Kumu will automatically create a field called "degree" and save the values

**Good to know:**

* To rerun metrics (for example, if you added new elements and connections), just follow the same steps again
* Metrics are run for all items that are *visible* on the map. If you want to exclude some elements from your metrics, simple filter them out before you run them
* To save multiple versions of the same metric, follow [this guide](/guides/metrics.md#saving-multiple-versions-of-a-single-metric)
* You can run any of the metrics mentioned [in this guide](/guides/metrics.md#sna-metrics), and then size based on them

## Size your elements

Once the metrics are calculated, you can size your elements by going into Settings on the right, and changing the "Size By" dropdown of the Basic Editor to the field of the metric you calculated (e.g. "degree"). More information on sizing can be found in [this guide](/guides/decorate/data-driven-decorations.md#size-by).

![size by metric](/files/r6XUjaychYRR4zoxMJ1C)


---

# 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://docs.kumu.io/frequently-asked-questions/how-do-i-size-elements-by-number-of-connections.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.