> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/faqs/how-can-i-add-a-clickable-link-to-a-metadata-field-in-the-uploader.md).
# How can I add a clickable link to a Metadata field in the Uploader?
Add clickable links to Metadata fields in the Uploader for additional guidance or resources
You can add a URL to the **Description** of a Metadata Entry to provide users with additional instructions, reference materials, or other useful resources while they are completing Asset metadata.
Once added, HIVO automatically detects the URL and displays itas a **clickable link in the Description of the corresponding Metadata field** when users reach the **Asset Details** step in the Uploader. The link opens in a **new browser tab**, so users can view the resource without leaving their upload.
### **How to add a link**
**🔹 Step 1: Go to Metadata Settings**
Go to **Client Profile → Settings → Metadata Settings**.
**🔹 Step 2: Find the Metadata Entry**
* Find the Metadata Entry where you want the link to appear.
* Each Metadata Entry has its own **Description**, so you can provide a different link for each Entry where required.
**🔹 Step 3: Add the link**
* Enter or paste the URL into the **Description** field.
* For example, you might link to:
* Metadata guidelines or instructions.
* A reference Asset or document in HIVO.
* An external resource users need when completing the field.
Finally, save the Metadata settings.
👉 **Note:** You can add, replace, or update the link at any time by editing the **Description** of the corresponding Metadata Entry in **Metadata Settings**.
If you have any questions, don't hesitate to ask, we're always here to help!
---
# 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://support.hivo.co/faqs/how-can-i-add-a-clickable-link-to-a-metadata-field-in-the-uploader.md?ask=&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.
.png?alt=media&token=b2076168-8c2e-4313-aec0-d4e79fc42fdd)
.png?alt=media&token=57f3cd30-bcae-4eea-b058-92eb32a20adc)