# Profiles

Every element, connection and loop has a **profile** that you can use to add narrative and any data that is important for you to track.

{% embed url="<https://www.youtube.com/embed/Nsu1vXD_v0s>" %}

By using [views](/guides/views.md) you can bring any of the information in the profile to life through [decorations](/guides/decorate.md), [filters](/guides/filter.md), [geo maps](/guides/templates/geo.md), and more. We'll look at each of the parts of the profile one by one:

<figure><img src="/files/6sE15vjhgm1qelEq3F8w" alt=""><figcaption></figcaption></figure>

## Default fields

Every profile shows a set of default fields at the top. Those fields are:

* Label
* Type
* Description
* Tags
* Image

To learn more about each of those fields and their purposes, check ouot [our full guide on fields](/guides/fields.md).

## Custom fields

The default fields are enough to get you started on most projects, but if you have other pieces of information like sector, net worth, or anything else, you can use the bottom section of the profile to create custom fields and fill them in with values.

Custom fields can also be grouped together using their "Category" setting. Assigning a category to a a field will make sure it is listed in that category in the profile. The most common example of this is [metrics](/guides/metrics.md) fields, which are assigned to the "Metrics" category by default:

![Screenshot of field category in the profile](/files/gUQrK2il0F2Ce2R6DJAU)

## Disabling the profile

You can choose to disable the profile entirely or only for specific elements and connections. To disable the profile for all elements and connections, use the `profile` property within `@settings`:

```scss
@settings {
  profile: false;
}

```

To enable the profile only for elements and connections that have a description field, you could use the following:

```scss
@settings {
  profile: false;
}

[description] {
  profile: true;
}
```

You can swap out `[description]` for any selector. Values for the `profile` property can be either `true` or `false`.


---

# Agent Instructions: 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:

```
GET https://docs.kumu.io/guides/profiles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.