> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/9.3-analytics/pentaho-analyzer-cp/advanced-topics/defining-hyperlinks-cp/create-hyperlinks-to-urls.md).

# Create hyperlinks to URLs

Perform the following steps to create hyperlinks to URLs:

1. Create an Analyzer report or open an existing one.
2. Right-click a row or column level and select **Hyperlink**.

   The Link on dialog box appears.
3. Click **Enable Link** to activate the hyperlink feature.

   You can disable linking by clearing the**Enable Link** check box.
4. In the **Link To** drop-down menu, select **URL** from the drop-down menu.
5. In the **URL** field, enter the full web address you want the hyperlink to launch.

   For example, '<http://www.example.com>.'
6. Choose how the URL displays by clicking on the **Open in** drop-down menu and selecting **New Tab**, **New Window**, or **Current Window**.
7. Enter a **Tool Tip** to be displayed when you hover over hyperlinks and click **OK**.

   The new hyperlinks appear in the Analyzer report.
8. Click the links to ensure the website associated with them appears correctly and save the report.


---

# 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.pentaho.com/pba/9.3-analytics/pentaho-analyzer-cp/advanced-topics/defining-hyperlinks-cp/create-hyperlinks-to-urls.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.