# Collibra

Use Collibra assets to configure the access request links into asset descriptions.

## Requirements

* [Connection registered in Immuta](/saas/configuration/integrations/data-and-integrations.md#registering-a-connection)
* Collibra user with a resource role with the **Asset** > **Update** resource permission, either directly for the asset or inherited from a parent community or domain.

## Set up access request links for assets

Follow the Collibra documentation to [Edit an asset](https://productresources.collibra.com/docs/collibra/latest/Content/Assets/ta_create-asset.htm#edit-an-asset) for every asset that you want data consumers to be able to request to access. Insert the [access request link](/saas/request/configure/how-to-guides/configure-access-request-links.md#access-request-links) for each asset into the asset **Description**.

{% hint style="info" %}
After completing the initial setup, add configuring the access request links to your data engineering pipelines.
{% endhint %}

## Set up access request links for data products

The first thing to consider when linking a catalog with data producs is how you appropriately represent a domain, data product, and data source in that catalog should it not have those object types. The most common approach with Collibra is the following:

* Domain (which contains the data product(s)) = Collibra Collection
* Data product (which contains the data source(s)) = Collibra Data Set
* Data source = Collibra Data Asset

A Collibra custom workflow can be leveraged to redirect to the Request app to request access. Download a sample workflow below. This workflow was exported in a way that allows you to import it and see its workflow "code" in the Collibra Workflow designer should you want to make changes.

{% hint style="warning" %}
This workflow is intended to be an example you can use and is not part of the Immuta software product nor SLAs.
{% endhint %}

{% file src="/files/yAP8RwyGRlLgJzw02BHK" %}

Once you are happy with the workflow "code", you must deploy it with the button at the top of the Collibra workflow designer. Then complete the setup:

1. Navigate to Settings, and then Workflows.
2. Find the newly deployed **Request Access Through Immuta** workflow and select it.
3. Uncheck "Show in global create"
4. This workflow "attaches" to a Data Set by configuring the "Applies To" in Collibra to a Data Set. You can change this to whatever object you represent data products with in Collibra.
5. Ensure the variables are empty
6. For the "Start Events" choose "Workflow Started"
7. Under "Other" ensure "Any user can start the workflow"
8. Save

Once complete, when you visit a Data Set in Collibra there will be a new action **Request Access through Immuta**. When clicked, a modal will appear asking to request access, and when selected, will dynamically redirect to the appropriate data product in the Immuta using the data product ID URL option. For data products, you must have a mirrored data product in Immuta [with the same ID as in Collibra](/saas/request/configure/how-to-guides/configure-access-request-links.md#resilient-data-product-mirroring).


---

# 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://documentation.immuta.com/saas/request/configure/how-to-guides/configure-access-request-links/collibra.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.