> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/forms/form-components/link.md). # Link The **Link** component adds a clickable relative or absolute hyperlink. Use this component to direct users to external websites, internal application pages, such as an asset page, documentation, or any other relevant URL. This component is for display purposes and does not store a value. ## General properties | Property | Description | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ID | The identifier of the component, primarily used for client-side interactions and identification in the HTML structure of the form. When you add a component, an ID is automatically generated to ensure it is unique in the form. | | Documentation | A text field for internal design notes or future reference about this specific component. This information is not visible in Collibra. | | Link text | A static or dynamic text to display as the link. | | Tab Index |

The tabbing order of this component in a user task form. When navigating through the form by pressing the Tab key, the cursor moves from one component to another based on their assigned tab index numbers. The component with the lowest tab index number receives focus first. The focus then moves sequentially to the component with the next highest number. For example, a component with a tab index of 1 receives focus before a component with a tab index of 2.

The tab index is ignored if the component is inside a subform.

| ## Validation properties | Attribute | Description | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Custom validations |

A list of additional validations for the component. Each custom validation consists of two parts:

For example, you can create a validation with the expression {{!(selection && selection.includes('None of the above') && selection.length > 1)}} to prevent combining a non-exclusive option with other selections. The expression describes the valid state, not the error condition. For more information on expression syntax and available JavaScript methods, see Form expressions.

| ## Rendering properties | Property | Description | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Navigation URL |

The URL to navigate to:

The link can also contain expressions, for example https\://\/asset/{{asset.value}}.

| | Ignored | Whether the component is be hidden in the form and any value it might hold is not included in the submission data. | | Target |

Where to open the linked document:

To respect the user browser preferences, don't specify any value for this attribute.

| | Visible | Whether the component is shown or hidden on the form. You can controlled this unconditionally or through an expression. For example, you can set an expression that hides or shows the component based on a user selection in another component. This property is enabled by default. | | Description | Additional information shown in Collibra below the form field, providing detailed instructions, examples, or essential guidance. | --- # 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://developer.collibra.com/workflows/designing-workflows/forms/form-components/link.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.