> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/integrations/collibra.md).

# Collibra

Overview of the bi-directional integration between Soda and Collibra: what it does, what it creates, and what you need to run it.

Bring Soda's data quality results into Collibra, and Collibra's governance context into Soda.

The Soda ↔ Collibra integration connects data quality execution in Soda with data governance in Collibra. Soda knows whether a table is trustworthy right now; Collibra is where people go to find out. The integration keeps the second answer honest.

## Capabilities

**Soda → Collibra.** Every check in scope becomes a governance asset in Collibra, carrying its latest result, its definition, when it last ran, a link back to Soda, and (where Soda reports them) the rows tested, passed and failed. Checks are linked to the table or column they test, to their data quality dimension, and to the data standard that generated them.

**Collibra → Soda.** Ownership, tags, dataset attributes and column-level business terms flow the other way, so the people and definitions that live in your glossary show up next to the checks in Soda.

Each direction is independently configurable, and every Collibra → Soda sync is off by default.

## Created assets

| Soda             | Collibra asset type                                               |
| ---------------- | ----------------------------------------------------------------- |
| Check or monitor | Data Quality Rule                                                 |
| Group-by check   | Data Quality Rule (the check) + one Data Quality Metric per group |
| Data standard    | Business Rule                                                     |

All three are configurable if your operating model uses custom types.

## Run sequence

The integration runs as a scheduled job — typically daily, shortly after your Soda scans finish. Each run reads your Soda Cloud organization, writes data quality assets into Collibra, and writes a small amount of governance metadata back into Soda.

It holds no state of its own: every run reconciles Collibra against whatever Soda currently says, so runs are repeatable and a second run over unchanged data does almost nothing. A dataset that fails does not stop the run.

## Requirements at a glance

* Python 3.10 or later, or the container image
* A Soda Cloud API key
* A Collibra user or OAuth application with permission to create and edit assets, attributes and relations
* Network access from wherever the job runs to both Soda Cloud and Collibra

Contact <support@soda.io> for access to the distribution.

## Documentation

|                                                                 |                                                                    |
| --------------------------------------------------------------- | ------------------------------------------------------------------ |
| [How it works](broken://pages/N2olF6JBzvvSr1UHT89H)             | What a run does, its scope, and what it does not do                |
| [Prerequisites](broken://pages/fo6AUNgXnLXoA6VOYVyW)            | What must exist in Soda and Collibra before you configure anything |
| [Setup](broken://pages/46l8iohZtc5njWj0UNyh)                    | Install, configure, and complete your first run                    |
| [Collibra operating model](broken://pages/wjJw7d9QpqB3HUXdVW0M) | Asset types, relation widening, and data quality scores            |
| [Configuration reference](broken://pages/GRr9RYqbuI74nuV3YAow)  | Every field in `config.yaml`                                       |

### Synchronized data

**Soda → Collibra**

|                                                            |                                                                            |
| ---------------------------------------------------------- | -------------------------------------------------------------------------- |
| [Checks and monitors](broken://pages/IBT09HEObxu54U38Jhih) | Every check becomes a Collibra asset with its result, definition and links |
| [Group-by checks](broken://pages/thQwowztU9ad5fkKfIY3)     | One rule asset plus one metric asset per group                             |
| [Data standards](broken://pages/ChiqAZX6I8gKJ9rhN4ih)      | Each standard becomes a Business Rule, linked to the checks it generates   |
| [Deleted checks](broken://pages/oRgsV9nQi5gDCoUVPfAO)      | Delete or mark obsolete when a check disappears from Soda                  |

**Collibra → Soda**

|                                                              |                                            |
| ------------------------------------------------------------ | ------------------------------------------ |
| [Dataset metadata](broken://pages/CVPHqS3m64xHBvVa0hAj)      | Owners, tags and dataset attributes        |
| [Column business terms](broken://pages/qnWgO9gKTfibLFBkNCym) | Glossary terms onto Soda column attributes |

### Running it

|                                                        |                                                |
| ------------------------------------------------------ | ---------------------------------------------- |
| [Deployment](broken://pages/wQUaS1SCQ6oEB5clHJqb)      | Kubernetes, Docker, AWS Lambda, and scheduling |
| [Troubleshooting](broken://pages/P4zL6ZJiMYQoCgIn1U5A) | Symptoms, causes, and what to check            |
| [FAQ](broken://pages/zvo38191o7eU8WkP1B0N)             | Common questions                               |

***

{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/reference/documentation-access-and-licensing.md).

If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.soda.io/integrations/collibra.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.