> 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-customize-link-text-in-popovers.md).

# How do I customize link text in popovers?

When you're designing [popovers](/guides/decorate/popovers.md), it's possible to include clickable links that take people to other webpages.

To do this, paste the link into a field, then [set the field's type to "URL"](/guides/fields.md#customize-a-field). Popovers will automatically recognize the link, and make it clickable:

![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-e70b492dcdb38f4d97dcd174833c0dce12152048%2Fpopover-link-raw.png?alt=media)

Often, it's nice to have custom text for these links too, instead of just the raw link. To accomplish that, you can take advantage of the fact that [popovers support Markdown syntax](/guides/decorate/popovers.md#using-markdown-to-style-the-popover). More specifically, you can enter a Markdown link, like the one you see below, into a field in a Kumu profile:

```
[Open Kumu's website](https://kumu.io)
```

Then, in Kumu, [set the field's type to "Text"](/guides/fields.md#customize-a-field). With that done, Kumu will show the custom link text in both the [profile](/guides/profiles.md) and in popovers.

![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-70e5552ec26ee31899bf8e26408349e302d6f7b6%2Fpopover-link-custom-text.png?alt=media)


---

# 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-customize-link-text-in-popovers.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.